CVE-2026-45293

published 28 Jul 2026 · updated 29 Jul 2026

WordPress Coding Standards (WordPressCS) contains an arbitrary code execution vulnerability

8.6HighCVSS 8.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
WordPressWordPress>=0.14.1 <3.4.1

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in WordPress, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-45293 severity on Zeptric[![CVE-2026-45293](https://zeptric.io/badge/cve/CVE-2026-45293.svg)](https://zeptric.io/cve/CVE-2026-45293)