A new WordPress core flaw called XSS2Shell (CVE-2026-64638) enables reflected pre-authentication XSS on the login page and can be chained into PHP code execution under specific conditions. WordPress versions through 7.0.2 and multiple earlier branches are affected, with public PoC code already circulating and urgent patching recommended for Italian public administration sites. #WordPress #XSS2Shell #CVE-2026-64638 #CERT-AGID #pwn.ai
Keypoints
- The vulnerability is a high-severity reflected XSS flaw in the WordPress core login page, tracked as CVE-2026-64638 and named XSS2Shell.
- Attackers can exploit inconsistent sanitization of user-controlled input, especially a crafted username, to trigger JavaScript execution in the WordPress domain.
- Researchers from pwn.ai showed that the XSS can be chained into a more complex attack path that may lead to PHP code execution on the server.
- Full compromise requires an authenticated WordPress administrator to interact with attacker-controlled content, making social engineering a key part of the chain.
- Public Proof-of-Concept code and a GitHub lab environment have been published, lowering the barrier to reproduction of the attack.
- WordPress releases prior to 7.0.3 and several earlier branches are affected; patches have been backported up to WordPress 4.7.34.
- CERT-AGID advises public administration organizations to update promptly and check for signs of compromise such as unknown Application Passwords, rogue plugins, and unexpected PHP files.
MITRE Techniques
- [T1059.007] Command and Scripting Interpreter: JavaScript ā The attacker can execute JavaScript in the context of the WordPress domain by abusing the reflected XSS on the login page. (āun attaccante può ottenere lāesecuzione di codice JavaScript nel contesto del dominio WordPress senza disporre preventivamente di credenziali valideā)
- [T1190] Exploit Public-Facing Application ā The flaw affects the public WordPress authentication page and can be triggered remotely through crafted input. (āvulnerabilità ⦠interessa la pagina di autenticazione di WordPressā)
- [T1056.002] Input Capture: GUI Input Capture ā The attack chain depends on an authenticated administrator interacting with an attacker-prepared page, enabling the attacker to abuse the victimās session. (ārichiede che un amministratore WordPress giĆ autenticato interagisca con una pagina predisposta dallāattaccanteā)
- [T1566.002] Phishing: Spearphishing Link ā Social engineering is required to lure the administrator into interacting with the malicious page. (ārichiede attivitĆ di social engineering e unāinterazione esplicita della vittimaā)
- [T1608.001] Stage Capabilities: Upload Malware ā The demonstrated chain includes uploading a plugin to the WordPress system as part of reaching PHP execution. (āal caricamento di un plugin e allāesecuzione di codice PHP sul serverā)
- [T1505.003] Server Software Component: Web Shell ā Post-compromise checks explicitly mention the possible presence of web shells or unrecognized PHP files on the site. (āpresenza di web shell o file PHP non riconducibili allāinstallazioneā)
Indicators of Compromise
- [CVE / Vulnerability ID] tracked flaw ā CVE-2026-64638, XSS2Shell
- [Software Versions] affected releases ā WordPress 7.0.2, WordPress 6.9.5, and 5 more affected branches
- [Software Versions] fixed releases ā WordPress 7.0.3, WordPress 6.9.6, and 5 more patched versions
- [Repository / Lab Environment] public reproduction material ā GitHub repository with a WordPress 7.0.2 lab, public PoC code
- [File Type] suspicious artifacts to look for ā unexpected PHP files, web shell files
- [Artifact / Account] compromise indicators ā unknown Application Passwords, newly created administrator accounts
- [Web Platform Artifacts] unauthorized changes ā unauthorized plugins, unauthorized themes