WordPress has released version 7.0.3, a security update that resolves 12 vulnerabilities in the core platform. The release targets cross-site scripting (XSS), server-side request forgery (SSRF), privilege escalation, and information disclosure risks, with fixes backported to all supported branches down to 4.7 where applicable.
What was fixed
The update addresses four distinct XSS vectors. A pre-authentication reflected XSS flaw on the login screen, tracked as CVE-2026-64638, could potentially lead to PHP code execution. Three additional stored XSS issues affect the Post Content block, Quick Edit interface on sites with large user bases, and the Post Date block, all requiring contributor-level access or higher. A separate privilege escalation bug in multisite networks with user registration enabled allows attackers to create new sites without proper authorization.
Other fixes include an SSRF vulnerability in URL validation that permits requests to link-local IP ranges, an information disclosure flaw in the Latest Comments block exposing comments on password-protected posts, and a bypass of the email address confirmation flow. The release also patches a CSS injection risk via a filter bypass in the safe CSS attribute system and an enumeration issue allowing disclosure of post slugs.
- 12 vulnerabilities patched in WordPress 7.0.3
- Pre-auth XSS on login screen (CVE-2026-64638) and SSRF in URL validation among critical fixes
- Backports in progress for branches 4.7 through 7.0
- Automatic updates rolling out to sites with background update support
- WordPress 7.1 RC2 also includes all applicable fixes
Update process and timeline
The security team released WordPress 7.0.3 on 6 August 2026. Sites supporting automatic background updates began receiving the patch shortly after publication. Manual updates can be initiated via the WordPress dashboard or by downloading the release directly from WordPress.org. The team is progressively backporting fixes to older branches, with WordPress 7.1 Release Candidate 2 already incorporating all relevant patches.
WordPress maintains that only the most recent major version receives active support, though security fixes are extended to older branches as a courtesy. The project credited 14 external researchers and multiple internal contributors for responsibly disclosing vulnerabilities and assisting with remediation.
Impact and recommendations
The vulnerabilities affect all WordPress installations running versions prior to 7.0.3, including multisite networks and sites using the block editor. While some flaws require authenticated access, the pre-auth XSS and SSRF risks present higher-severity exposure for unpatched sites. Operators of high-traffic or multisite environments should prioritize testing and deployment, particularly where user registration is enabled.
For professionals: Sites using custom login pages or plugins that modify the login flow should verify compatibility with the patched XSS protections. The SSRF fix may affect plugins or themes that rely on URL validation for internal requests; test integrations that interact with link-local or private IP ranges.
The WordPress Security Team has not reported active exploitation of these vulnerabilities at the time of release. However, the public disclosure of technical details in the CVE and GHSA advisories increases the likelihood of targeted attacks against unpatched installations.
Companies mentioned
Automated pipeline · Security
Synthesized from 1 industry feed on 6 Aug 2026. Passed independent editor verification (score 95/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — Deduped batch of 2 candidates
- Checking for duplicates — New story No recent or in-pipeline article covers a WordPress 7.0.3 security release.
- Checking for duplicates — New story pre_write:; No existing article covers WordPress 7.0.3 security release.
- Writing the article — Draft created article_id=401 slug=wordpress-7-0-3-patches-12-security-flaws
-
Editor review — Approved
- Score: 95/100
- Factual grounding: The CVE identifier 'CVE-2026-64638' is correctly cited, but the source does not explicitly state it is for the pre-auth XSS on the login screen. The source lists the vulnerability and the CVE/GHSA reference separately, so the direct association is inferred. This is defensible but should be noted.
- Style compliance: The 'Key facts' block includes 'WordPress 7.1 RC2 also includes all applicable fixes,' which is not a hard number/date and could be moved to prose. However, this is a minor stylistic choice and does not violate core rules.
- No copied phrasing: The phrase 'pre-authentication reflected XSS flaw on the login screen' closely mirrors the source's 'Pre-auth reflected cross-site scripting (XSS) on the login screen.' While the meaning is identical, the phrasing should be further paraphrased to avoid echoing the source.
- Generating reader Q&A — Generated 5 items
- Assigning hero image — Reused library image reused image #155
- Linking related stories — Linked 2 relations from 344 candidates
- Publishing — Published wordpress-7-0-3-patches-12-security-flaws
- Mastodon — Posted https://mstdn.social/@hostingpaper/117050309454636859



Discussion · coming soon
Be the first to join the thread when community discussion launches.