# CVE-2026-64638 — WordPress

> As of 2026-08-07, CVE-2026-64638 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in WordPress, CVSS v4.0 8.9. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-64638, most recently “WordPress Core XSS2Shell Vulnerability Chains Pre-Auth XSS to RCE (CVE-2026-64638)”.

**Last updated:** 2026-08-07

## What is CVE-2026-64638?

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

The record classifies CVE-2026-64638 under weakness class [CWE-79](https://cwe.mitre.org/data/definitions/79.html). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 37 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 8.9 — High (derived from score) (`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 KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-08-07

## Is CVE-2026-64638 being exploited?

Weaponised exploit code for CVE-2026-64638 is publicly available. 3 public proof-of-concept repositories are tracked for this identifier.

- [Boreas37/CVE-2026-64638-PoC](https://github.com/Boreas37/CVE-2026-64638-PoC) (github)
- [686f6c61/POC-WP-XSS2Shell-CVE-2026-64638](https://github.com/686f6c61/POC-WP-XSS2Shell-CVE-2026-64638) (github)
- [wordsec/XSS2Shell](https://github.com/wordsec/XSS2Shell) (github)

## Affected products and versions

- **WordPress**: WordPress

## How to fix CVE-2026-64638

No vendor patch reference has been recorded for CVE-2026-64638 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-64638

1 tracked threat in the Threadlinqs corpus references CVE-2026-64638, either in the campaign’s CVE list or as an indicator on the campaign record.

- [WordPress Core XSS2Shell Vulnerability Chains Pre-Auth XSS to RCE (CVE-2026-64638)](https://intel.threadlinqs.com/threat/TL-2026-1933) — HIGH · 2026-08-07

## Sources

Enriched from CVE.org, NVD, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-08-07. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [hackerone.com](https://hackerone.com/reports/3877102)
- [wordpress.org](https://wordpress.org/news/2026/08/wordpress-7-0-3-release/)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-64638
Full detection coverage and IOCs for threats exploiting CVE-2026-64638 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp