On this page (7 sections)
The WordPress project published version 7.1.5 on November 18, 2026 and calls it a security release. The WordPress.org announcement says it contains fixes for multiple issues and advises updating immediately.
Everyone who runs WordPress should plan the update. Multisite operators and sites with public comments or reachable XML-RPC have the most reason to hurry. The announcement gives no CVE identifiers and no severity scores, so this article describes each fix only at the level of detail the release notes provide.
At a glance
What the release fixes
The announcement lists 20 items. Here they are grouped by weakness type instead of the order used in the post. No technical write-ups accompany them, so the mechanics of each flaw are not public in the material we have. Reporter credits are in the release post.
Code execution, SQL injection and privilege escalation
- Unauthenticated privilege escalation via Template Part block attributes, which could lead to remote code execution (reporter: Logan Homolka).
- SQL injection in WP_Meta_Query through nested relation values (reporter: Christiaan Swiers).
- SQL injection through the front page setting in Customizer changeset previews (reporter: Rudy Faile, WordPress Security Team).
- Multisite privilege escalation: a site Administrator could take over a Super Admin account through Customizer menu previews (reporter: Yuval Miller).
Cross-site scripting (XSS)
- Unauthenticated stored XSS via shortcode attributes in comments (reporter: Rafie Muhammad, Awesome Motive, Inc.).
- Reflected XSS in the legacy media library popup (reporter: Anthropic).
- XSS in wp_interactivity_data_wp_context() through the store namespace (reporter: Juliette Reinders Folmer).
- Contributor+ XSS via scripts in oEmbed provider responses (reporter: vvh1te3zz).
- Administrator stored XSS via Customizer previews (reporter: Weston Ruter, WordPress Security Team).
- Contributor+ stored XSS in the Comment Date block via its date format (reporters: Weston Ruter and Jeremy Felt, WordPress Security Team).
- XSS in the block editor via Openverse image metadata (reporter: Shu Takahashi, Velcore Consulting Inc.).
- Contributor+ stored XSS in the block editor via media filenames when a media block is converted to a File block (reporter: CryptoFox).
Information disclosure, authorization and denial of service
- Unauthenticated exposure of private taxonomy terms through the REST API search endpoint (reporter: Anthropic).
- Author+ exposure of user email addresses through the REST API comments endpoint (reporter: Ben Bidner, WordPress Security Team).
- Editor+ information disclosure via post and template author assignment in the REST API (reporter: Jarda Snajdr, WordPress Security Team).
- Subscriber+ information disclosure via XML-RPC wp.getComments (reporter: Jaewook Lee).
- Author+ authorization bypass through comment editing in the admin (reporter: Jesse McNeil).
- Unauthenticated denial of service via batched XML-RPC pingbacks (reporter: Giovanni Cintolo).
Hardening changes
- A malformed regular expression that broadened JSON media type matching was fixed as hardening (reporter: Mo Jangda, WordPress Security Team).
- The block editor's Imgur embed variation was removed because its server-side provider is already gone.
- The WordPress 7.0 removal of 1024 bit certificates from the bundled root certificates has now been applied to 6.9.12 and earlier.
Who is realistically exposed
Labels such as Unauthenticated, Subscriber+ or Contributor+ indicate the lowest role needed to trigger an issue. Unauthenticated items matter most on public sites since no login is required. In this release they are the Template Part privilege escalation, the stored XSS in comments, the XML-RPC pingback denial of service and the REST API taxonomy disclosure.
Sites that allow open registration, or that have many low-privilege accounts, should still take the Subscriber+ and Contributor+ items seriously, because such accounts are easy to obtain. Multisite operators have a specific concern: the Super Admin takeover begins with a site Administrator, a role that on many networks is held by a customer or client.
How to check your exposure
First identify which version each site runs. The two WP-CLI commands below are read-only and should be run from the WordPress root directory. The first prints the installed version; the second reports whether a core update is available.
wp core versionwp core check-updateOn the 7.1 branch, any version below 7.1.5 lacks these fixes. For older branches, the announcement says backports are in progress and will ship as they become ready, so check again later. It also reminds readers that only the most recent WordPress version is actively supported.
The Updates screen in the Dashboard shows the same thing. If you manage many sites, build an inventory and flag which are multisite, allow open registration or expose XML-RPC.
What to do now
- Back up the site files and database.
- Update to WordPress 7.1.5 from Dashboard > Updates or by downloading it from WordPress.org. Automatic background updates may begin by themselves, but verify that the update completed.
- If you cannot run 7.1.x, apply the update for your branch when its backport ships, and plan a move to a supported version.
- Run wp core version to confirm the new version number.
- On multisite, review the Super Admin list and recent changes to menus and Customizer settings for anything unfamiliar.
- Audit Contributor, Author, Editor and Administrator accounts and remove those no longer needed.
- Scan recent comments for odd shortcode-like content and remove anything suspicious.
- If XML-RPC is not needed, restrict access to it at the web server or firewall.
If you prefer the command line, the next command applies the core update once your backup is complete. Afterwards, rerun the version check and load both the front page and the admin area to confirm everything works.
wp core updateWordPress 7.2 is planned for December 8th, and 7.2 RC 2 has been released with all applicable fixes, according to the announcement. A release candidate is not intended for production, so do not install it only to obtain these patches.
Detection and monitoring afterwards
Because no exploit details are published, there is no specific signature to search for. General warning signs still apply: new administrator or Super Admin accounts you did not create, unfamiliar files in wp-content, comments with script content, spikes in requests to xmlrpc.php, and heavy traffic to REST API search and comments endpoints.
The following read-only command counts lines mentioning xmlrpc.php in an Nginx access log. Change the path to match your server (Apache keeps logs elsewhere) and compare the result with your normal baseline.
grep -c "xmlrpc.php" /var/log/nginx/access.logA sharp rise above your usual level deserves attention, given the XML-RPC pingback denial of service fixed here. A web application firewall adds a layer in front of WordPress, as explained in what is a WAF, but it is no substitute for updating. If you suspect a site was already compromised, follow website hacked: what to do.
For ongoing visibility, Webforta Monitor tracks uptime, certificates, DNS and header changes, which can help you notice side effects of a failed update or an incident.
Timeline
| Date | Event |
|---|---|
| 2026-11-18 | WordPress 7.1.5 security release published on WordPress.org |
| In progress | Backports of the security fixes to all branches eligible for them (currently through 4.7), shipping as they become ready |
| Planned 2026-12-08 | WordPress 7.2 major release (7.2 RC 2 already released) |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
