CVE-2026-64638: XSS2Shell
CVE-2026-64638, known as XSS2Shell, is a pre-authentication reflected cross-site scripting vulnerability in the WordPress Core login screen. A crafted username submitted during a failed login passes through inconsistent HTML sanitization: PHP strip_tags(), invoked through WordPress username sanitization, preserves malformed tag-like input that subsequent WordPress KSES processing interprets as permitted HTML. This allows attacker-controlled DOM elements to appear in the login error message. Built-in JavaScript behavior, DOM clobbering, and REST API JSONP responses can then be combined to execute JavaScript in the WordPress origin. Under additional conditions involving an authenticated administrator and explicit victim interaction, the vulnerability can be chained into server-side PHP execution. WordPress 7.0.3 fixes the issue, with fixes also available for older branches back to 4.7.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation enables JavaScript execution in a victim's browser under the affected WordPress site's origin. Against an authenticated administrator, the demonstrated escalation can authorize and disclose an Application Password, publish attacker-controlled script content, and upload executable PHP through plugin installation functionality. This can compromise the WordPress instance and expose database credentials, permit unauthorized administrator-account creation and content modification, and enable operating-system commands with the web-server process's privileges. Server-side execution is conditional, not an unauthenticated, interaction-free outcome.
Mitigation
If you can’t patch tonight, do this now.
No vendor-specific temporary workaround is documented. Applying the applicable WordPress or distribution security update is the established corrective action.
Remediation
Patch, then assume compromise.
Upgrade to WordPress 7.0.3 or a later fixed release. Alternatively, install the corresponding security backport for the deployed branch; fixes extend back through WordPress 4.7. Examples include 6.9.6, 6.8.7, 6.7.6, and 4.7.34. Installations older than 4.7 should migrate to a fixed release rather than assume a backport exists. For Debian 13 (trixie) installations using the distribution package, upgrade wordpress to 6.8.7+dfsg1-0+deb13u1 or a later Debian security update.
Exploits
26 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit. Showing the 25 most capable, earliest first.
Frequently asked questions
- Is CVE-2026-64638 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-64638?
- Yes. Mallory tracks 26 public exploits or proofs of concept for CVE-2026-64638, the earliest disclosed Aug 7, 2026.
- Is there a patch for CVE-2026-64638?
- Upgrade to WordPress 7.0.3 or a later fixed release. Alternatively, install the corresponding security backport for the deployed branch; fixes extend back through WordPress 4.7.
- How severe is CVE-2026-64638?
- CVE-2026-64638 has a CVSS v4 score of 8.9 (High) and an EPSS score of 0.89% (60th percentile) as of Nov 17, 2026.
Recent activity
114 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.