WordPress Login Page Exposed to Critical XSS2Shell Flaw CVE-2026-64638: Over 11,000 Sites Attacked Across 67 Countries
WordPress core login page has been hit by a high-severity reflected XSS vulnerability tracked as CVE-2026-64638, dubbed XSS2Shell by researchers. The issue affects every supported version and requires no credentials to trigger, enabling attackers to execute JavaScript in the site origin and potentially seize full server control.
At 2 a.m., a cross-border e-commerce operator was awakened by monitoring alerts after an unknown administrator account appeared on his three-year-old WordPress site alongside an unrecognized plugin file. Despite using a 16-character random password and IP whitelisting, the attacker had bypassed all defenses through the daily login page itself.
Vulnerability Mechanics
On August 6, WordPress released version 7.0.3 containing the fix for CVE-2026-64638 (CVSS 8.9). The root cause lies in inconsistent HTML filtering on the login form: when a nonexistent username is submitted, the entered value is reflected in the error message. One sanitization pass treats a crafted tag as cleaned, while the second pass renders it as executable HTML, allowing the payload to persist and run.
Imperva telemetry shows organized automated attacks targeting more than 11,000 sites across 67 countries, generating hundreds of thousands of requests. 95 percent of observed tooling is written in Go; 75 percent of victims are U.S.-based, with gaming (32 percent), education (26 percent), and finance (24 percent) sectors hit hardest.
Attack Chain: From XSS to Shell
The exploit begins with a crafted username that triggers the reflected XSS. Once JavaScript executes under the site origin, the attacker leverages loaded WordPress scripts and the REST API to interact with the application. If an administrator session is active, the attacker can obtain an application password, create a malicious page, and upload a PHP backdoor plugin, completing server takeover.
Researchers note that the full chain benefits from social engineering, such as phishing emails disguised as official security notices. The attack path was assembled in roughly four days using open-source AI models and multi-agent workflows, highlighting the accelerating role of AI in exploit development.
Self-Check Steps for Administrators
- Verify version: Check the footer in the dashboard; upgrade 7.0.x to 7.0.3 and apply backports (6.9.6, 6.8.7, 6.7.6) down to the 4.7 branch.
- Audit accounts: Review the user list for unknown administrators and inspect Application Passwords for unauthorized entries.
- Inspect files: Examine the wp-content/plugins directory for unexpected additions and monitor file modification timestamps.
Organizations using Cloudflare or other WAF solutions should confirm that virtual patching rules for CVE-2026-64638 are active. The advisory reference is GHSA-52p2-r8wf-jcrf.
Related articles
Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison
An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.
VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server
Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.
September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication
The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.
API Token Lifecycle: From Issuance to Revocation and Secure Management
The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.