WordPress 7.1.5 Fixes 20 Security Issues, Including a Path to Remote Code Execution
WordPress 7.1.5 (18 November 2026) fixes 20 security items in core. What changed, which versions are patched, and how to check a site that missed the earlier 7.1.4 fix.
WordPress released version 7.1.5 on 18 November 2026. It is a security release that fixes 20 items in WordPress core, and the project asks every site to update straight away. The most serious fix closes a privilege escalation that needs no account and, according to the release notes, "could lead to remote code execution".
No attacks using the new issues had been reported when this article was written (21 November 2026). A different core flaw, fixed three weeks earlier in 7.1.4, is being exploited, so sites that skipped that update are the ones most at risk today. Both are covered below.
What you should do now
- Check your version. Open Dashboard → Updates. A current site shows 7.1.5, or the patched release of its own branch (see the table further down).
- Update if it has not happened automatically. Click "Update Now". Sites with automatic background updates should already have started updating, but confirm it rather than assume.
- Review who can edit. Six of the fixes concern Contributor, Author or Editor accounts. Remove accounts you no longer need and downgrade those with more access than their job requires.
- On multisite, review site administrators. One fix stops a site Administrator from taking over a Super Admin account.
- Check PHP separately. Updating WordPress does not update PHP, and PHP shipped its own critical fixes on 19 November. See our article on the PHP-FPM flaw.
The most serious fix
WordPress describes it as an "unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution", reported by Logan Homolka.
Patchstack's analysis of the patch adds an important condition. The attacker does not need an account, but a logged-in user with at least Editor access has to open the crafted content in the block editor. The editor then sends requests using that user's session, and they can be steered to other parts of the site's REST API. If the person who opens the content is an administrator, the reachable endpoints include plugin installation, which is how code execution becomes possible. This is Patchstack's reading of the code; WordPress has not published technical details.
In practice: until you have updated, do not open submitted or pending content from sources you do not trust while logged in as an administrator.
What else was fixed
The release post lists 20 items. Patchstack counts them as 18 vulnerabilities and two hardening changes.
| Type | Who could use it | Fix |
|---|---|---|
| Privilege escalation, possible code execution | No account (needs an editor to open content) | Template Part block attributes |
| Stored cross-site scripting | No account | Shortcode attributes in comments |
| Denial of service | No account | Batched XML-RPC pingbacks |
| Information disclosure | No account | Private taxonomy terms via the REST search endpoint |
| SQL injection | Not stated by WordPress | Nested relation values in WP_Meta_Query |
| SQL injection | Not stated by WordPress | Front page setting in Customizer changeset previews |
| Privilege escalation (multisite) | Site Administrator | Super Admin takeover via Customizer menu previews |
| Stored cross-site scripting | Contributor or higher | oEmbed provider responses, the Comment Date block, media filenames in the File block |
| Information disclosure | Subscriber, Author or Editor | XML-RPC wp.getComments, REST comments endpoint (user emails), post and template author assignment |
| Authorization bypass | Author or higher | Comment editing in the admin |
| Cross-site scripting | Varies | Legacy media library popup, Interactivity API context, Openverse image metadata, Customizer previews |
| Hardening | n/a | JSON media type matching; Imgur embed variation removed from the block editor |
WordPress has not assigned CVE identifiers or severity scores to these issues. Patchstack and CovertSwarm both noted that none existed on 18–19 November.
Patched versions for older branches
WordPress back-ported the fixes to every branch it still secures. Branches 6.5 to 7.0 are affected by all 20 items; older branches by fewer. Version 4.6 and earlier receive no security updates.
| Branch | Patched release | Branch | Patched release |
|---|---|---|---|
| 7.1 | 7.1.5 | 6.3 | 6.3.15 |
| 7.0 | 7.0.9 | 6.2 | 6.2.16 |
| 6.9 | 6.9.12 | 6.1 | 6.1.17 |
| 6.8 | 6.8.13 | 6.0 | 6.0.19 |
| 6.7 | 6.7.12 | 5.9 | 5.9.21 |
| 6.6 | 6.6.12 | 5.8 | 5.8.20 |
| 6.5 | 6.5.15 | 4.9 | 4.9.36 |
| 6.4 | 6.4.15 | 4.7 | 4.7.40 |
The full list, including the 5.0 to 5.7 and 4.8 branches, is on the WordPress 7.1.5 version page linked in the sources. WordPress 7.2 RC 2 carries the same fixes; the final 7.2 release is planned for 8 December 2026.
The flaw that is being exploited: CVE-2026-119977
WordPress 7.1.4, released on 28 October 2026, fixed a weakness in the core update process. While a full core update runs, files are unpacked into a predictable folder under wp-content/upgrade/, and for a few seconds an outsider can run the staged setup-config.php. The affected versions are 4.7.0 to 7.1.3.
Beazley Security reports that attack attempts began within hours of the release and that the US agency CISA added the flaw to its Known Exploited Vulnerabilities catalog on 3 November 2026. We could not open CISA's own page, so that date comes from Beazley.
If your site was updated to 7.1.4 or later, the hole is closed. Updating does not show whether someone got in during an earlier update. Beazley suggests searching the web server logs for requests to the staging folder:
grep -E "wp-content/upgrade/.*\.php" /var/log/nginx/access.log* /var/log/apache2/access.log*
grep "setup-config.php" /var/log/nginx/access.log* /var/log/apache2/access.log*
Repeated requests across many folder names around the time of a core update are the pattern to look for. If you find them, check for administrator accounts you do not recognise, unexpected plugins or PHP files, and changed configuration, and rotate the database password.
Update from the command line
On a VPS with WP-CLI installed, run these from the site's folder as the user that owns the files:
wp core version
wp core update
wp core update-db
wp core verify-checksums
verify-checksums compares core files with the official release and reports any that were changed or added.
Sources
- WordPress.org: WordPress 7.1.5 release (18 November 2026)
- WordPress.org: Version 7.1.5 (patched releases per branch)
- Patchstack: WordPress 7.1.5 security release
- CovertSwarm: WordPress core 7.1.5 security release (19 November 2026)
- WordPress.org: WordPress 7.1.4 (28 October 2026)
- Beazley Security: advisory BSL-A1241 on CVE-2026-119977 (4 November 2026)
Wordfence has also published analysis of both releases. Its pages could not be read when we prepared this article, so no Wordfence figures are used here.