Loading vulnerability…
CVE-2026-45293 is an arbitrary code execution vulnerability in WordPress Coding Standards (WordPressCS), a PHP_CodeSniffer ruleset for enforcing WordPress coding conventions. Affected versions from 0.14.1 up to, but not including, 3.4.1 contain unsafe logic in the WordPress.WP.EnqueuedResourceParameters sniff, active in the WordPress and WordPress-Extra rulesets. The vulnerable is_falsy() logic reconstructs the $ver argument supplied to enqueue-related functions and evaluates it with eval(). When PHPCS scans attacker-controlled or otherwise untrusted PHP source, a crafted expression in that argument can be executed on the scanning host during linting or standards enforcement. The issue does not affect the WordPress-Core or WordPress-Docs rulesets. The flaw was fixed by removing eval()-based handling and replacing it with explicit token-level checks for a limited set of literal falsy values in version 3.4.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical code injection vulnerability in WordPress Coding Standards (WordPressCS) prior to version 3.4.2. The flaw is caused by unsafe use of eval() on a reconstructed ver argument in the WordPress.WP.EnqueuedResourceParameters sniff, allowing arbitrary code execution on the scanning host during code analysis.
An arbitrary command execution vulnerability in WordPress Coding Standards caused by unsafe use of eval() in the WordPress.WP.EnqueuedResourceParameters sniff when scanning untrusted PHP code.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.