CVE-2026-45293
WordPress Coding Standards is a set of PHP_CodeSniffer rules …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/WordPress/WordPress-Coding-Standards/commit/a29048d0bbef5cf25d42349c74e4072d3cb
- github.com/WordPress/WordPress-Coding-Standards/pull/2771
- github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.4.1
- github.com/WordPress/WordPress-Coding-Standards/security/advisories/GHSA-3pwp-g2mj-5p3v
- github.com/advisories/GHSA-3pwp-g2mj-5p3v
- nvd.nist.gov/vuln/detail/CVE-2026-45293
- cve.org/CVERecord?id=CVE-2026-45293
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.