CVE-2026-45293

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 29, 2026

Advisory Details (4)

Auto-updated Jul 28, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Arbitrary code execution via eval() in the EnqueuedResourceParameters sniff · Advisory · WordPress/WordPress-Coding-Standards · GitHub

https://github.com/WordPress/WordPress-Coding-Standards/security/advisories/GHSA-3pwp-g2mj-5p3v
github_release Patch Available

3.4.1 - 2026-07-27

Patch available: WordPress/WordPress-Coding-Standards 3.4.1

https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.4.1
github_pr Patch Available

WP/EnqueuedResourceParameters: remove eval() from is_falsy()

Patch available: WordPress/WordPress-Coding-Standards 3.4.1 (PR #2771 merged 2026-07-27)

https://github.com/WordPress/WordPress-Coding-Standards/pull/2771
github_commit Patch Available

commit a29048d0bbef (WordPress/WordPress-Coding-Standards)

Patch available: WordPress/WordPress-Coding-Standards 3.4.1 (contains commit a29048d0bbef)

https://github.com/WordPress/WordPress-Coding-Standards/commit/a29048d0bbef5cf25d42349c74e4072d3cbc8325

Vendor Advisories for CVE-2026-45293(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
wp-coding-standards/wpcs0.14.1 ... 3.4.0 (18 versions)3.4.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 15:46 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:53 UTCEG score recompute
  4. 2026-08-23 01:24 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 00:30 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 23:35 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 22:40 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 21:45 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 19:56 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 18:51 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 06:18 UTCEG score recompute
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 05:25 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 04:31 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 15:06 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 30 more
  1. 2026-08-11 14:12 UTCEG score recompute
  2. 2026-08-11 01:45 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-10 00:51 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 23:58 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 23:03 UTCEG score recompute
  9. 2026-08-06 22:07 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 21:13 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 20:18 UTCEG score recompute
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:38 UTCEPSS rescore
  16. 2026-08-03 19:21 UTCEG score recompute
  17. 2026-08-03 10:36 UTCEPSS rescore
  18. 2026-08-02 06:00 UTCEG score recompute
  19. 2026-08-02 02:27 UTCEPSS rescore
  20. 2026-08-01 05:06 UTCEG score recompute
  21. 2026-08-01 04:16 UTCEPSS rescore
  22. 2026-07-31 04:10 UTCEG score recompute
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 15:43 UTCEG score recompute
  25. 2026-07-30 02:47 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 14:20 UTCEG score recompute
  28. 2026-07-29 13:59 UTCEG score recompute
  29. 2026-07-29 04:45 UTCEG score recompute
  30. 2026-07-28 15:22 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45293?
CVE-2026-45293 is a high vulnerability published on July 28, 2026. WordPress Coding Standards is a set of PHPCodeSniffer 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…
When was CVE-2026-45293 disclosed?
CVE-2026-45293 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45293 actively exploited?
CVE-2026-45293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.0% of all scored CVEs.
What is the CVSS score of CVE-2026-45293?
CVE-2026-45293 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-45293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45293, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45293

Explore →

Is Your Infrastructure Affected by CVE-2026-45293?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs