CVE-2026-64638

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.9Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.9HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity89% × 45%
Impact severity (EG Severity): CVSS 8.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is its impact severity (EG Severity), not escalated.

EG Severity
8.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 7, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available.
Web page

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 rangeFix by version rangeDependents
wordpress5.7.1+dfsg1-2 ... 7.0.3+dfsg1-1 (42 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress6.1.1+dfsg1-1 ... 7.1.2+dfsg1-1 (30 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress6.8.1+dfsg1-1, 6.8.3+dfsg1-0+deb13u1, 6.8.3+dfsg1-1, 6.8.6+dfsg1-0+deb13u1
  • every version up to 6.8.7+dfsg1-0+deb13u1: fixed in 6.8.7+dfsg1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress6.8.1+dfsg1-1 ... 7.0.2+dfsg1-1 (6 versions)
  • every version up to 7.0.3+dfsg1-1: fixed in 7.0.3+dfsg1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 112 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-18 03:22 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-13 11:38 UTCEG score recompute
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-12 15:47 UTCEG score recompute
  12. 2026-10-11 19:32 UTCEG score recompute
  13. 2026-10-11 16:47 UTCEG score recompute
  14. 2026-10-11 14:08 UTCEG score recompute
  15. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-06 23:17 UTCEG score recompute
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-05 19:28 UTCEG score recompute
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-05 08:14 UTCEG score recompute
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 58th percentile
Show 75 more
  1. 2026-10-04 05:43 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-03 01:00 UTCEG score recompute
  4. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-02 09:33 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-09-30 22:55 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-09-29 05:45 UTCEG score recompute
  10. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-09-27 17:09 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-09-25 04:15 UTCEG score recompute
  14. 2026-09-23 21:16 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescoreEPSS 31% · 98th percentile
  16. 2026-09-22 22:54 UTCEG score recompute
  17. 2026-09-22 00:42 UTCEG score recompute
  18. 2026-09-19 23:57 UTCEG score recompute
  19. 2026-09-19 00:18 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 31% · 98th percentile
  21. 2026-09-18 02:12 UTCEG score recompute
  22. 2026-09-17 00:53 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 31% · 98th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 31% · 98th percentile
  25. 2026-09-15 14:15 UTCEG score recompute
  26. 2026-09-13 00:55 UTCEG score recompute
  27. 2026-09-11 15:47 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 31% · 98th percentile
  29. 2026-09-11 09:37 UTCEPSS rescoreEPSS 31% · 98th percentile
  30. 2026-09-10 17:37 UTCEG score recompute
  31. 2026-09-09 06:00 UTCEG score recompute
  32. 2026-09-08 22:01 UTCEPSS rescoreEPSS 31% · 98th percentile
  33. 2026-09-06 14:17 UTCEG score recompute
  34. 2026-09-06 13:47 UTCEPSS rescoreEPSS 31% · 98th percentile
  35. 2026-09-05 16:10 UTCEG score recompute
  36. 2026-09-05 15:31 UTCEPSS rescoreEPSS 31% · 98th percentile
  37. 2026-09-05 02:22 UTCEG score recompute
  38. 2026-09-04 09:02 UTCEG score recompute
  39. 2026-09-04 05:07 UTCEPSS rescoreEPSS 31% · 98th percentile
  40. 2026-09-03 05:59 UTCEG score recompute
  41. 2026-09-02 14:12 UTCEPSS rescoreEPSS 31% · 98th percentile
  42. 2026-09-01 17:38 UTCEG score recompute
  43. 2026-09-01 13:54 UTCEPSS rescoreEPSS 31% · 98th percentile
  44. 2026-09-01 04:40 UTCEPSS rescoreEPSS 31% · 98th percentile
  45. 2026-08-30 19:30 UTCEG score recompute
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 31% · 98th percentile
  47. 2026-08-30 08:28 UTCEG score recompute
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 31% · 98th percentile
  49. 2026-08-29 10:23 UTCEG score recompute
  50. 2026-08-28 21:42 UTCEPSS rescoreEPSS 31% · 98th percentile
  51. 2026-08-26 16:32 UTCEG score recompute
  52. 2026-08-26 14:47 UTCEPSS rescoreEPSS 31% · 98th percentile
  53. 2026-08-25 18:21 UTCEG score recompute
  54. 2026-08-25 13:49 UTCEPSS rescoreEPSS 31% · 98th percentile
  55. 2026-08-24 20:15 UTCEG score recompute
  56. 2026-08-23 11:05 UTCEG score recompute
  57. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  58. 2026-08-22 01:59 UTCEG score recompute
  59. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  60. 2026-08-21 03:54 UTCEG score recompute
  61. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  62. 2026-08-19 18:47 UTCEG score recompute
  63. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  64. 2026-08-18 20:20 UTCEG score recompute
  65. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  66. 2026-08-17 22:14 UTCEG score recompute
  67. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  68. 2026-08-17 00:10 UTCEG score recompute
  69. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  70. 2026-08-16 13:08 UTCEG score recompute
  71. 2026-08-15 04:02 UTCEG score recompute
  72. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  73. 2026-08-14 05:57 UTCEG score recompute
  74. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  75. 2026-08-12 20:51 UTCEG score recompute

Publicly available exploits

(12 references, 10 shown)

Public exploit code is referenced for this CVE (11 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoC0xlipon/xss2shell
    Published Aug 9, 2026

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

    Open source ↗
  • GitHub PoCeh-amish/CVE-2026-64638-XSS-to-Shell-PoC
    Published Aug 9, 2026
    Open source ↗
  • GitHub PoCg0d150ne/XSS2Shell
    Published Aug 9, 2026

    XSS2Shell ULTIMATE v3.0 is a powerful exploitation tool that chains Cross-Site Scripting (XSS) vulnerabilities in WordPress to achieve Remote Code Execution (RCE). This tool exploits CVE-2026-64638 to gain full control over vulnerable WordPress installations.

    Open source ↗
  • GitHub PoCHackSpeak/CVE-2026-64638
    Published Aug 8, 2026

    XSS2Shell (CVE-2026-64638) WordPress pre-auth XSS to RCE PoC mirror — WordSec, MIT; for authorized security testing

    Open source ↗
  • GitHub PoCimbas007/CVE-2026-64638-POC
    Published Aug 8, 2026

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

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

    CVE-2026-64638

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

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

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

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

    Open source ↗
  • GitHub PoCLinuxhackingid-official/XSS2Shell-CVE-2026-64638
    Published 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
    Published 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 ↗

Frequently asked(5)

What is CVE-2026-64638?
CVE-2026-64638 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-64638 published?
The CVE record for CVE-2026-64638 was published on August 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-64638 actively exploited?
CVE-2026-64638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64638?
CVE-2026-64638 has a CVSS base score of 8.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64638?
A fix for CVE-2026-64638 is available: update to the fixed version the vendor names in its advisory.

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.