WordPress 7.1.5 Security Release: 20 Vulnerabilities Fixed and Recommended Actions
WordPress released version 7.1.5 on November 18, 2026, a security release that fixes 20 issues in WordPress core and the block editor. Update every site now. Fixes have been backported to every branch still eligible for security updates, back to WordPress 4.7.
The most serious issue is an unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution (RCE). An attacker doesn't need a WordPress account to reach it. The release also closes a multisite flaw that let a site Administrator take over a Super Admin account, two SQL injections, and an unauthenticated stored XSS in comments.
| Severity | Critical (unauthenticated privilege escalation with possible RCE) |
| Status | Patches available as of November 18, 2026 |
| Fixed in | WordPress 7.1.5, plus backports to every branch from 7.0 down to 4.7 |
| Issues fixed | 20 (18 vulnerabilities and 2 hardening changes) |
| Unauthenticated issues | 4: privilege escalation/RCE, stored XSS, information disclosure, denial of service |
| CVEs / CVSS | Not published at the time of writing |
| Exploited in the wild | Yes. Monarx has observed more than 44,000 probe and exploit attempts in the past 24 hours |
Attackers are already moving. Before WordPress published the release, our Threat Research team created several virtual patching rules covering all of the vulnerabilities fixed in 7.1.5, so Monarx customers were protected from day one. Over the past 24 hours, those rules have recorded more than 44,000 attempts to probe or exploit these vulnerabilities across our hosting partner network.
Affected and fixed versions
Every WordPress version before 7.1.5 is affected by some or all of these issues. Older branches are affected by fewer, because some vulnerable features don't exist there. Upgrade to 7.1.5, or to the fixed release for the branch you run:
| Branch | Issues that apply | Fixed in |
|---|---|---|
| 7.1 | 20 | 7.1.5 |
| 7.0 | 20 | 7.0.9 |
| 6.9 | 20 | 6.9.12 |
| 6.8 | 20 | 6.8.13 |
| 6.7 | 20 | 6.7.12 |
| 6.6 | 20 | 6.6.12 |
| 6.5 | 20 | 6.5.15 |
| 6.4 | 19 | 6.4.15 |
| 6.3 | 19 | 6.3.15 |
| 6.2 | 19 | 6.2.16 |
| 6.1 | 18 | 6.1.17 |
| 6.0 | 18 | 6.0.19 |
| 5.9 | 17 | 5.9.21 |
| 5.8 | 15 | 5.8.20 |
| 5.7 | 15 | 5.7.22 |
| 5.6 | 15 | 5.6.24 |
| 5.5 | 13 | 5.5.25 |
| 5.4 | 13 | 5.4.26 |
| 5.3 | 13 | 5.3.28 |
| 5.2 | 13 | 5.2.31 |
| 5.1 | 13 | 5.1.29 |
| 5.0 | 12 | 5.0.32 |
| 4.9 | 12 | 4.9.36 |
| 4.8 | 12 | 4.8.35 |
| 4.7 | 11 | 4.7.40 |
| 4.6 and earlier | — | No security updates |
Source: WordPress 7.1.5 release documentation
A few notes:
- Only the latest version is actively supported. Backports are a safety net, not a long-term plan.
- Two branches get extra fixes. The 6.0 branch picks up fixes from WordPress 6.9.2 that it had missed, and the 5.7 branch fixes a lodash mismatch: it shipped lodash 4.17.19 while the script loader reported 4.17.21.
- WordPress 6.9.12 and earlier also drop 1024-bit certificates from the bundled root certificate store, a change that first shipped in WordPress 7.0.
- Gutenberg plugin: a new Gutenberg release ships with all the relevant block editor fixes. If you run the plugin, update it too.
- WordPress 7.2 is planned for December 8. RC 2 already includes these fixes, but don't wait for 7.2 to patch.
What was fixed
WordPress hasn't published CVE IDs or severity scores yet, so the most useful way to triage is by who can reach each bug. An issue an anonymous visitor can trigger is far more dangerous than one that needs an Editor account.
The critical issues
Unauthenticated privilege escalation via Template Part block attributes (GB#138). An attacker without a WordPress account could abuse Template Part block attributes to gain privileges they shouldn't have, which could lead to remote code execution. This is the top priority in the release. Reported by Logan Homolka.
Multisite privilege escalation via Customizer menu previews (WP#2092). On a multisite network, an Administrator of a single site could take over a Super Admin account, turning control of one site into control of the entire network. It requires an authenticated site Administrator, but on networks where site admins are customers or untrusted users, that's a real boundary. Reported by Yuval Miller.
Two SQL injections in core (WP#2117, WP#2055). One is in the front page setting in Customizer changeset previews, reported by Rudy Faile. The other is in WP_Meta_Query via nested relation values, reported by Christiaan Swiers. WP_Meta_Query is used by core and by countless plugins, so its real-world reach depends on how plugins pass user input into meta queries.
Unauthenticated stored XSS via shortcode attributes in comments (WP#1729). Anyone who can post a comment could store a script that runs when the comment is viewed, including by an administrator moderating it. Reported by Rafie Muhammad.
All fixes by required access
| Required access | ID | Issue |
|---|---|---|
| Unauthenticated | GB#138 | Privilege escalation via Template Part block attributes that could lead to RCE |
| Unauthenticated | WP#1729 | Stored XSS via shortcode attributes in comments |
| Unauthenticated | WP#1191 | Private taxonomy terms exposed via the REST API search endpoint |
| Unauthenticated | WP#2377 | Denial of service via batched XML-RPC pingbacks |
| Not specified | WP#2055 | SQL injection in WP_Meta_Query via nested relation values |
| Not specified | WP#2131 | Reflected XSS in the legacy media library popup |
| Not specified | WP#2611 | XSS in wp_interactivity_data_wp_context() via the store namespace |
| Not specified | GB#250 | XSS in the block editor via Openverse image metadata |
| Subscriber+ | WP#1333 | Information disclosure via XML-RPC wp.getComments |
| Contributor+ | WP#1550 | XSS via scripts in oEmbed provider responses |
| Contributor+ | GB#167 | Stored XSS in the Comment Date block via its date format |
| Contributor+ | GB#414 | Stored XSS via media filenames when converting an Image, Audio, or Video block to a File block |
| Author+ | WP#1315 | User email addresses exposed via the REST API comments endpoint |
| Author+ | WP#2177 | Authorization bypass via comment editing in the admin |
| Editor+ | WP#2930 | Information disclosure via post and template author assignment in the REST API |
| Administrator | WP#2092 | Multisite: site Administrator can take over a Super Admin account via Customizer menu previews |
| Administrator | WP#2117 | SQL injection via the front page setting in Customizer changeset previews |
| Administrator | WP#283 | Stored XSS via Customizer previews |
| Hardening | WP#1297 | Malformed regular expression that broadened JSON media type matching |
| Hardening | GB#336 | Removal of the block editor's Imgur embed variation, whose server-side provider is gone |
IDs prefixed WP are core fixes; GB are block editor (Gutenberg) fixes. Access levels come from the official release notes; "Not specified" means WordPress didn't state one.
Exploitation status
Exploitation is already underway. In the past 24 hours, Monarx has recorded more than 44,000 attempts to probe or exploit the vulnerabilities fixed in 7.1.5 across sites protected by our hosting partners. There are still no CVE IDs and, as far as we know, no public proof-of-concept code, which tells us attackers are working straight from the patch. Here is why the window closed so fast:
- The patch is public. The 7.1.5 diff touches 19 core files, from
class-wp-meta-query.phpto the REST API search handler andshortcodes.php. Attackers diff security releases to find the bugs. - Four issues need no account. The Template Part privilege escalation, the comment stored XSS, the taxonomy disclosure, and the XML-RPC pingback DoS can all be reached by anonymous visitors, which makes them easy to scan for at scale.
- Stored XSS is a takeover path. A script planted in a comment runs in the browser of whoever views it. If that's an administrator, the attacker can create users, install plugins, or edit theme files, which is how XSS turns into a backdoor.
- This is the second short-cycle release in a row. WordPress 7.1.4 fixed a separate code execution path in the core upgrade process. Sites that skipped 7.1.4 are behind on both.
Recommended actions
1. Update now
Update to WordPress 7.1.5 from Dashboard → Updates → Update Now, or with WP-CLI:
wp core update --minor
wp core versionIf you can't move to 7.1.x yet, install the latest release for your branch from the table above (for example, 7.0.9 or 6.9.12). If you run the Gutenberg plugin, update it as well.
2. Verify, don't assume
Most sites receive security releases through automatic background updates, but auto-updates fail silently more often than people think: file permission problems, AUTOMATIC_UPDATER_DISABLED or WP_AUTO_UPDATE_CORE set to false, version control checkouts, or a host that disables them. Check the version on every install:
# Check every WordPress install under a path
for d in /home/*/public_html; do echo "$d: $(wp core version --path=$d 2>/dev/null)"; done3. Reduce exposure until patched
If a site can't be updated immediately:
- Disable XML-RPC if it isn't needed (Jetpack and some mobile apps rely on it). This blocks the pingback DoS and the
wp.getCommentsdisclosure. - Hold comments for moderation, or temporarily close them, to limit the unauthenticated stored XSS.
- Review user roles. Remove stale Contributor, Author, and Editor accounts; several fixes need only those roles.
- On multisite networks, audit who holds site Administrator roles and confirm Super Admin accounts haven't changed.
4. Look for signs of compromise
Patching closes the door, but it doesn't tell you whether someone already got in. Look for new administrator accounts, unexpected Super Admins, unfamiliar plugins or must-use plugins, modified theme files, and <script> tags in comments or post content.
For hosting providers
- Inventory WordPress core versions across your fleet, including installs stuck on old branches.
- Push 7.1.5 (or the branch backport) to managed sites, and flag customer-managed sites where auto-updates are disabled.
- Prioritize multisite networks and sites with open comment forms.
- Notify customers on WordPress 4.6 and earlier: they get no security fixes at all.
- Watch for scanning against the Template Part block, REST API search, and XML-RPC endpoints in the days after release.
How Monarx helps
To be clear: Monarx does not replace updating WordPress. These are bugs in WordPress core, and installing 7.1.5 or your branch's backport is the only complete fix.
What Monarx does is cover the gap between disclosure and patch, and catch what attackers do after a successful exploit. A privilege escalation, SQL injection, or admin-targeted XSS is rarely the end goal. Attackers use it to plant backdoors, malicious plugins, webshells, and injected JavaScript that keep them on the site long after the bug is fixed. That's where ThreatShield works:
Monarx customers were protected before the release. Ahead of WordPress 7.1.5's publication, our Threat Research team built several virtual patching rules that cover every vulnerability in this release. They block exploit attempts at the request level, so even sites that haven't updated yet are shielded. In the past 24 hours, these rules have caught more than 44,000 attempts to probe or exploit the 7.1.5 vulnerabilities.
- Runtime protection: ThreatShield watches PHP as it executes and blocks malicious code before it runs, including webshells and backdoors dropped through an exploit.
- Detection and cleanup: Our engine detects malicious and obfuscated files across the server, including in plugin, theme, and upload directories, and can remove or quarantine them automatically.
- Visibility for hosting partners: Our Threat Research team monitors signals across our partner network and ships new detections as exploitation patterns emerge.
If you're a hosting provider and want to protect your customers' WordPress sites while updates roll out, contact us to learn how ThreatShield works with your platform.
Conclusion
WordPress 7.1.5 is a release to install today, not at the next maintenance window. Four of its 20 fixes need no account, one of those could lead to remote code execution, and we've already seen more than 44,000 attempts to probe or exploit these vulnerabilities in a single day. Update every site, verify the version actually changed, and keep an eye out for signs of compromise.
We'll update this advisory as CVE IDs, new exploitation data, or new guidance emerge.
Ready for next‑gen AI Server Security?
Start your Monarx journey in minutes