CVE-2026-45293

Arbitrary code execution via evaluated version argument

Published Jul 28, 2026 · Updated Jul 28, 2026

Code injection in WordPress Coding Standards 0.14.1 through 3.4.0 allows attackers to execute code when PHPCS scans crafted PHP. The WordPress.WP.EnqueuedResourceParameters sniff reconstructs the untrusted $ver argument and passes it to eval() while deciding whether the value is falsy. Exploitation requires PHPCS to scan attacker-controlled code with the WordPress or WordPress-Extra ruleset and executes with the scanning process privileges; WordPress-Core and WordPress-Docs are unaffected.

CVSS severity8.6
High
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in WordPress Coding Standards 0.14.1 through 3.4.0 allows attackers to execute code when PHPCS scans crafted PHP. The WordPress.WP.EnqueuedResourceParameters sniff reconstructs the untrusted $ver argument and passes it to eval() while deciding whether the value is falsy. Exploitation requires PHPCS to scan attacker-controlled code with the WordPress or WordPress-Extra ruleset and executes with the scanning process privileges; WordPress-Core and WordPress-Docs are unaffected.

The record

CVE
CVE-2026-45293
Published
Jul 28, 2026
Updated
Jul 28, 2026
Vendor
WordPress.org
Product
WordPress Coding Standards
Classifications
CWE-95, T1203
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 0.14.1, < 3.4.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

WordPress.org · WordPress Coding Standardsversion=>= 0.14.1, < 3.4.1

Published CVSS scores

8.6GitHubCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo