cve.bz

CVE-2026-64638 (XSS2Shell) Cross-site Scripting

8.9 highEPSS 0.9%

Known as XSS2Shell

High (8.9). EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
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](https://pwn.ai/).

Severity

CVSS 4.0

8.9 high
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-64638 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64638?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64638?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64638 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12wordpressno fix listedDEBIAN-CVE-2026-64638
Debian13wordpress6.8.7+dfsg1-0+deb13u1DEBIAN-CVE-2026-64638 DSA-6427-1
Debian14wordpress7.0.3+dfsg1-1DEBIAN-CVE-2026-64638
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morewordpressno fix listedUBUNTU-CVE-2026-64638

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Boreas37/CVE-2026-64638-PoC-XSS2Shell- Harbor Check: matches CVE 130 stars, Python, created
    XSS2Shell (CVE-2026-64638) WordPress pre-auth XSS to RCE chain — PoC exploit + defensive audit tool + nuclei template
  • wordsec/XSS2Shell Harbor Check: matches CVE 6 stars, created
    Wordpress Pre-auth XSS to RCE exploit PoC (xss2shell & CVE-2026-64638)
  • 0xlipon/xss2shell Harbor Check: matches CVE 3 stars, created
    🔥 XSS2Shell — CVE-2026-64638 Scanner & PoC Toolkit
  • eh-amish/CVE-2026-64638-XSS-to-Shell-PoC Harbor Check: matches CVE 3 stars, Python, created
  • tc4dy/CVE-2026-64638-PoC-Exploit Harbor Check: matches CVE 3 stars, Python, created
    CVE-2026-64638 - WordPress Security Assessment Suite (CVSS 8.9) | WordPress 4.7.0-7.0.2 pentest toolkit. Includes vulnerability assessment …
22 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Nuclei template WordPress Core < 7.0.3 - Preauth Reflected XSS (XSS2Shell)
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Wordpress wp-login.php Rest API JSONP Reflected Cross Site Scripting Attempt M1 (CVE-2026-64638) sid 2072578
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Wordpress wp-login.php Rest API JSONP Reflected Cross Site Scripting Attempt M2 (CVE-2026-64638) sid 2072579
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Wordpress wp-login.php Rest API JSONP Reflected Cross Site Scripting Attempt M3 (CVE-2026-64638) sid 2072580

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON