1-minute read of a 5 min report

Failed WordPress Login Input Reaches Conditional Server Code Execution

By

1-minute read

What a defender needs to know

WordPress 7.0.3 fixes CVE-2026-64638, a reflected XSS flaw on the public login screen. Every earlier WordPress version is affected. One failed login can run attacker-controlled JavaScript in the site’s origin without an account, but the published path to PHP execution also requires a logged-in administrator to visit and interact with a malicious third-party page.

The flaw begins with parser disagreement. PHP tag stripping treats a whitespace-tag construction as text, while WordPress KSES reparses it as allowed HTML. Injected elements then match selectors in user-profile.js, trigger a click, replace the undefined ajaxurl through browser named properties, and steer jQuery to a REST JSONP response that it evaluates as JavaScript.

Inventory every production, staging, recovery, and forgotten site. Confirm 7.0.3 or a fixed backport from the running instance. Match the deployment record to that running version on every site. Preserve proxy, web, PHP, WordPress audit, endpoint, and file-integrity evidence before cleanup. For valuable sites, account for failed-login input, administrator sessions, Application Passwords, posts, plugin uploads, PHP changes, and outbound traffic across the exposure window. Revoke unexplained Application Passwords and rotate administrator secrets from a clean system.

The blind spot is the administrator’s path through the page. Check the current patch status and separately investigate administrator sessions from before the update.

Primary sources