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/).
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-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
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.
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.
tc4dy/CVE-2026-64638-PoC-ExploitHarbor Check: matches CVE3 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
renzi25031469/CVE-2026-64638-WordPress-Core-XSS2ShellHarbor Check: matches CVE3 stars, created Template Nuclei para detecção não-intrusiva do XSS2Shell, um parser differential pré-autenticado no WordPress Core que permite injeção de e…
5yu4n/CVE-2026-64638Harbor Check: matches CVE3 stars, Python, created CVE-2026-64638
g0d150ne/XSS2ShellHarbor Check: matches CVE2 stars, created XSS2Shell ULTIMATE v3.0 is a powerful exploitation tool that chains Cross-Site Scripting (XSS) vulnerabilities in WordPress to achieve Remo…
HackSpeak/CVE-2026-64638Harbor Check: matches CVE2 stars, Python, created XSS2Shell (CVE-2026-64638) WordPress pre-auth XSS to RCE PoC mirror — WordSec, MIT; for authorized security testing
madfxr/xss2shell-pocHarbor Check: matches CVE1 star, created XSS2Shell: WordPress Preauth XSS to RCE Chain (CVE-2026-64638)
SanaullahAmanullah/xss2shell-checkHarbor Check: matches CVE1 star, created Non-destructive detector for CVE-2026-64638 (XSS2Shell) — WordPress pre-auth XSS reflection primitive
Alixploit22/CVEX2SHELHarbor Check: matches CVE0 stars, created CVE-2026-64638 adalah kerentanan Pre-Auth Reflected Cross-Site Scripting (XSS) di WordPress yang ditemukan pada tahun 2026. Kerentanan ini …
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.
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.