CVE-2026-45293
RCE in WordPress Coding Standards PHPCS sniff via eval when scanning untrusted PHP.
Is CVE-2026-45293 being exploited?
Not confirmed. CVE-2026-45293 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-45293?
CVE-2026-45293 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-45293?
Yes. A fix has been recorded for CVE-2026-45293. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45293 affect?
CVE-2026-45293 affects WordPress Coding Standards (phpcs ruleset) versions 0.14.1–3.4.0, PHPCS using WordPress or WordPress-Extra rulesets, CI pipelines linting untrusted PHP, Developer workstations running PHPCS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45293?
Upgrade to WordPress-Coding-Standards >=3.4.1; avoid scanning untrusted code and isolate CI runners.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on scanning hosts: crafted $ver input triggers eval() allowing arbitrary command execution during PHPCS scans.
Immediate action required
- affected>= 0.14.1 and < 3.4.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.