security: update WordPress core to 7.0.3 - #445
Merged
Merged
Conversation
WordPress 7.0.3 is a security release fixing vulnerabilities disclosed on 2026-08-06, including a pre-auth reflected XSS on the login screen with potential to lead to PHP code execution (CVE-2026-64638, GHSA-52p2-r8wf-jcrf, CVSS 8.9 High). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
roots/wordpress/roots/wordpress-no-content7.0 → 7.0.3.WordPress 7.0.3 (released 2026-08-06) is a security release fixing 12 vulnerabilities; the fixes were backported to every supported branch, and
7.0.3is the patched release for this site's branch. The headline issue: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. Affects all WordPress 4.7.0–7.0.2.The remaining issues (4× Contributor+ stored XSS, multisite privilege escalation, SSRF in URL validation, Author+ CSS injection, two info-disclosure issues, post slug enumeration, email confirmation bypass) all require at least a contributor account or are lower impact.
Why this is a manual PR: the nightly vulnerability scan will not catch this yet — no advisory for WordPress core has been published to the Packagist / wpsecadv databases that
composer auditreads, so the scan currently reports clean.Stays within this repo's existing
composer.jsonconstraint — lock-only change, no minor/major jump.🤖 Generated with Claude Code