wp-coding-standards/wpcs vulnerabilities
PHP_CodeSniffer rules (sniffs) to enforce WordPress coding conventions
- Registry
- Composer
- Latest
- 3.4.1
- License
- MIT
1 known advisory
The latest version, 3.4.1, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require wp-coding-standards/wpcs:^3.4.1Is your project on an affected wp-coding-standards/wpcs?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for wp-coding-standards/wpcs
WordPress Coding Standards (WordPressCS) contains an arbitrary code execution vulnerability
- Affected
- >=0.14.1 <3.4.1
- Fixed in
- 3.4.1
Is your wp-coding-standards/wpcs version vulnerable?
- wp-coding-standards/wpcs 3.4No known advisories in 3.4.1
- wp-coding-standards/wpcs 3.31 advisory in 3.3.0
- wp-coding-standards/wpcs 3.21 advisory in 3.2.0
- wp-coding-standards/wpcs 3.11 advisory in 3.1.0
- wp-coding-standards/wpcs 3.01 advisory in 3.0.1
- wp-coding-standards/wpcs 2.31 advisory in 2.3.0
- wp-coding-standards/wpcs 2.21 advisory in 2.2.1
- wp-coding-standards/wpcs 2.11 advisory in 2.1.1
- wp-coding-standards/wpcs 2.01 advisory in 2.0.0
- wp-coding-standards/wpcs 1.21 advisory in 1.2.1
- wp-coding-standards/wpcs 1.11 advisory in 1.1.0
- wp-coding-standards/wpcs 1.01 advisory in 1.0.0
Which of your client projects still run an old wp-coding-standards/wpcs?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.