CVE-2026-64638

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 31.2%, top 2% 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
Elevated
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 31%CVSS: 8.9Exploit: Elevated riskExposed: 0

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

WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control. This requires successful social engineering of and explicit interaction by the target victim. This issue affects all versions of WordPress. Version 7.0.3 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7. Discovered and responsibly disclosed by the team at pwn.ai.

CVSS v3
8.9
EG Score
8.9(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity89% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
31%
EPSS %ILE
98%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

WordPress 7.0.3 release – WordPress News

https://wordpress.org/news/2026/08/wordpress-7-0-3-release/

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wordpress5.7.1+dfsg1-2 ... 7.0.3+dfsg1-1 (42 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wordpress6.1.1+dfsg1-1 ... 7.0.3+dfsg1-1 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wordpress6.8.1+dfsg1-1 ... 7.0.3+dfsg1-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wordpress6.8.1+dfsg1-1 ... 7.0.3+dfsg1-1 (7 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 10:23 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 16:32 UTCEG score recompute
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-25 18:21 UTCEG score recompute
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-24 20:15 UTCEG score recompute
  9. 2026-08-23 11:05 UTCEG score recompute
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 01:59 UTCEG score recompute
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 03:54 UTCEG score recompute
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 18:47 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 20:20 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 22:14 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 00:10 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 13:08 UTCEG score recompute
  24. 2026-08-15 04:02 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 15 more
  1. 2026-08-14 05:57 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 20:51 UTCEG score recompute
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-11 22:47 UTCEG score recompute
  6. 2026-08-11 00:43 UTCEG score recompute
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-09 15:37 UTCEG score recompute
  9. 2026-08-09 13:47 UTCEPSS rescore
  10. 2026-08-08 17:33 UTCEG score recompute
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 19:28 UTCEG score recompute
  13. 2026-08-07 18:26 UTCEG score recompute
  14. 2026-08-07 18:07 UTCEG score recompute
  15. 2026-08-07 18:07 UTCMITRE cvelistV5first tracked

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xlipon/xss2shell
    First seen Aug 9, 2026

    🔥 XSS2Shell — CVE-2026-64638 Scanner & PoC Toolkit

    Open source ↗
  • GitHub PoCeh-amish/CVE-2026-64638-XSS-to-Shell-PoC
    First seen Aug 9, 2026
    Open source ↗
  • GitHub PoCimbas007/CVE-2026-64638-POC
    First seen Aug 8, 2026

    CVE-2026-64638: WordPress Pre-auth XSS → RCE (XSS2Shell) PoC

    Open source ↗
  • GitHub PoCBoreas37/CVE-2026-64638-PoC-XSS2Shell-
    First seen Aug 7, 2026

    XSS2Shell (CVE-2026-64638) WordPress pre-auth XSS to RCE chain — PoC exploit + defensive audit tool + nuclei template

    Open source ↗
  • GitHub PoCwordsec/XSS2Shell
    First seen Aug 7, 2026

    Wordpress Pre-auth XSS to RCE exploit PoC (xss2shell & CVE-2026-64638)

    Open source ↗
  • GitHub PoC5yu4n/CVE-2026-64638
    First seen Aug 7, 2026

    CVE-2026-64638

    Open source ↗
  • GitHub PoCLinuxhackingid-official/XSS2Shell-CVE-2026-64638
    First seen Aug 7, 2026

    CVE-2026-64638 — WordPress Pre-Auth Reflected XSS → RCE via DOM Clobbering + Application Password Theft + REST API Plugin Activation. Dual-mode PoC (XSS chain & direct).

    Open source ↗
  • GitHub PoCrenzi25031469/CVE-2026-64638-WordPress-Core-XSS2Shell
    First seen Aug 7, 2026

    Template Nuclei para detecção não-intrusiva do XSS2Shell, um parser differential pré-autenticado no WordPress Core que permite injeção de elementos DOM na página de login, servindo de base para uma cadeia de XSS → RCE.

    Open source ↗
  • GitHub PoCBoreas37/CVE-2026-64638-PoC
    First seen Aug 7, 2026

    XSS2Shell (CVE-2026-64638) PoC — WordPress pre-auth XSS to RCE chain

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-64638.yaml
    First seen Jan 1, 2026

    WordPress Core < 7.0.3 - Preauth Reflected XSS (XSS2Shell)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64638?
CVE-2026-64638 is a high vulnerability published on August 7, 2026. WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control. This requires…
When was CVE-2026-64638 disclosed?
CVE-2026-64638 was first published in the National Vulnerability Database on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64638 actively exploited?
CVE-2026-64638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31% probability of exploitation in the next 30 days, which ranks it in the top 1.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64638?
CVE-2026-64638 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-64638?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64638, 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-64638

Explore →

Is Your Infrastructure Affected by CVE-2026-64638?

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

Start Free Scan →Browse All CVEs