CVE-2026-64638: XSS2Shell
CVE-2026-64638 is a pre-authentication reflected cross-site scripting vulnerability in the WordPress Core login screen, known as XSS2Shell. A crafted username submitted during a failed login passes through inconsistent HTML parsers: PHP strip_tags(), invoked through WordPress username sanitization, preserves certain malformed tag-like strings that wp_kses_post() subsequently interprets as permitted HTML. This allows attacker-controlled DOM elements into the login error response. Built-in password-generation and profile handlers, DOM clobbering, and REST API JSONP behavior can then be combined to execute JavaScript in the WordPress origin. With an authenticated administrator's explicit interaction and additional environmental conditions, the XSS can be chained into arbitrary server-side PHP execution. Unpatched WordPress releases are affected; version 7.0.3 and corresponding backported security releases through the 4.7 branch contain fixes.
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 executes attacker-controlled JavaScript 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 the plugin installation workflow. Resulting server-side execution occurs with the web-server process's privileges and can enable access to database credentials and other application secrets, creation of administrator accounts, modification of site content, and operating-system command execution. Server-side compromise is conditional on administrator interaction and site capabilities; the initial unauthenticated XSS is not a browser-independent unauthenticated RCE.
Mitigation
If you can’t patch tonight, do this now.
No separate validated workaround is specified. Apply the vendor or distribution security update promptly rather than relying on temporary filtering measures.
Remediation
Patch, then assume compromise.
Upgrade WordPress to version 7.0.3 or later, or install the corresponding fixed release for the deployed branch. Backported fixes extend through WordPress 4.7, including releases 6.9.6, 6.8.7, 6.7.6, and 4.7.34. Installations older than 4.7 should migrate to a fixed release. For Debian stable (trixie), upgrade the wordpress package to 6.8.7+dfsg1-0+deb13u1 or a later security-fixed package.
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 Oct 27, 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 WordPress to version 7.0.3 or later, or install the corresponding fixed release for the deployed branch. Backported fixes extend through WordPress 4.7, including releases 6.9.6, 6.8.7, 6.7.6, and 4.7.34.
- 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 Oct 27, 2026.
Recent activity
113 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.