What’s Vulnerable › Vulnerabilities

CVE-2026-45293: WordPress Coding Standards (WordPressCS) contains an arbitrary code execution vulnerability

• Severity: high (CVSS 8.6 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-28 · updated 2026-10-24
• Weakness: CWE-95

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.

Affected products

• WordPress-Coding-Standards: from 0.14.1, < 3.4.1

References

• https://github.com/WordPress/WordPress-Coding-Standards/commit/a29048d0bbef5cf25d42349c74e4072d3cbc8325
• https://github.com/WordPress/WordPress-Coding-Standards/pull/2771
• https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.4.1
• https://github.com/WordPress/WordPress-Coding-Standards/security/advisories/GHSA-3pwp-g2mj-5p3v

Get alerted when CVE-2026-45293 or the next vulnerability affects your stack