WordPress released 7.1.5 on November 18 and recommends updating sites immediately. Its core security fixes cover public attack paths as well as weaknesses requiring an existing account. Verify the completed core update on each installation, including multisite networks.
The release documentation confirms the date and backport versions. This is a new security release, separate from the earlier upgrade-window vulnerability already covered here.
Public exposure and account roles change the risk
The project’s release notes identify several fixes worth separating:
- Unauthenticated privilege escalation through Template Part block attributes, which WordPress says could lead to remote code execution. The public notes do not give a complete configuration or exploitability matrix.
- Unauthenticated stored cross-site scripting through shortcode attributes in comments. Stored cross-site scripting lets attacker-supplied content run as script when a browser displays it.
- Unauthenticated denial of service through batched XML-RPC pingbacks, an interface used for remote application calls and link notifications.
- Unauthenticated disclosure of private taxonomy terms through REST API search. Taxonomy terms organize site content; their private status should survive access through the application’s API.
- Multisite privilege escalation through Customizer menu previews. A site Administrator could take over a Super Admin account, crossing from one site’s authority into network-wide control.
Other repairs address SQL injection, which can alter database queries, along with script injection, authorization and information-disclosure issues. Some require Contributor, Author, Editor or Administrator privileges. Treating every listed issue as an anonymous takeover would misstate the release.
Evidence status: vulnerabilities and repairs confirmed by the affected project’s release notes. Those notes provide no confirmed in-the-wild exploitation report or victim count for this set. The exploitation report in the older desk article concerns a different vulnerability.
Verify a repair on the branch actually deployed
The current release is 7.1.5. WordPress says sites supporting automatic background updates will begin updating automatically. That statement does not establish completion on an individual installation.
For operators:
- Check Dashboard → Updates and confirm the resulting core version. Include every separate WordPress installation, not just the main domain.
- Use the exact backport for an older branch while planning an upgrade. The official documentation lists 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12 and 6.5.15, with further branch-specific repairs down through 4.7.40.
- Do not assume each older branch has identical exposure. WordPress’s documentation lists different affected-issue counts across branches. It says 4.6 and earlier no longer receive security updates, and only the newest version is actively supported.
- Check normal site behavior after updating, including publishing, comments and any remote clients that depend on XML-RPC or the REST API.
The announcement says backports ship as they become ready. Use the release documentation’s named build for the deployed branch and verify its availability through the normal update channel. Staying on an old branch indefinitely is a separate maintenance risk.
These are core repairs. A core version check does not establish the safety of installed themes, plugins or credentials. Suspicious accounts or changed files still need investigation; an update alone cannot explain away earlier compromise.
Caveat: The release notes omit detailed reproduction conditions for several public attack paths. Prioritize the documented update without inventing CVE identifiers, attack counts or a universal takeover scenario.