CVE-2026-45293 WordPress Coding Standards (WordPressCS) contains an arbitrary code execution vulnerability
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
- Technology
- PHPWordPress
Description
WordPress Coding Standards is a set of PHP_CodeSniffer rules (sniffs) that enforce WordPress coding conventions. From 0.14.1 until 3.4.1, the WordPress.WP.EnqueuedResourceParameters sniff (active in the WordPress and WordPress-Extra rulesets) reconstructed the $ver argument passed to functions such as wp_enqueue_script() and ran it through eval() inside its is_falsy() method, so a maliciously crafted argument such as 'system'('id') would execute during a scan; as a result, running PHPCS with WordPressCS over untrusted PHP (for example a CI pipeline that lints pull requests, or a developer reviewing third-party code) could lead to arbitrary command execution on the scanning host. The WordPress-Core and WordPress-Docs rulesets are not affected. This issue is fixed in version 3.4.1.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| wp-coding-standards/wpcs(Packagist) | = 0.14.1; = 1.0.0; = 1.1.0; = 1.2.0 +15 more | 3.4.1 | Fixed |
| WordPress-Coding-Standards | = >= 0.14.1, < 3.4.1 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| wp-coding-standards/wpcs(Packagist) | >= 0.14.1, < 3.4.1 | 3.4.1 |
| wp-coding-standards/wpcs(Packagist) | = 0.14.1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 1.0.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 1.1.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 1.2.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 1.2.1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.0.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.0.0-RC1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.1.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.1.1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.2.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.2.1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 2.3.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.0.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.0.1 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.1.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.2.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.3.0 | No fix listed |
| wp-coding-standards/wpcs(Packagist) | = 3.4.0 | No fix listed |
| WordPress-Coding-Standards | = >= 0.14.1, < 3.4.1 | No fix listed |
References
- https://github.com/WordPress/WordPress-Coding-Standards/security/advisories/GHSA-3pwp-g2mj-5p3v vendor-advisory
- https://github.com/WordPress/WordPress-Coding-Standards/pull/2771 patch
- https://github.com/WordPress/WordPress-Coding-Standards/commit/a29048d0bbef5cf25d42349c74e4072d3cbc8325 patch
- github.com product
- https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.4.1
- github.com