TL;DR
- WordPress.org lists 20 items in 7.1.5: 18 vulnerabilities and 2 hardening changes, released on 18 November 2026.
- Four of the 20 need no login, led by a Template Part block privilege escalation that WordPress.org says could lead to remote code execution.
- Nine fixes need a logged-in role, from Subscriber+ up to a multisite Administrator able to take over a Super Admin account.
- Fixes are being backported to every branch back to 4.7, and WordPress 7.2 RC 2 carries them; WordPress 7.2 is planned for 8 December 2026.
WordPress.org released WordPress 7.1.5 on 18 November 2026 as a security release with 20 fixes, and it recommends that every site update immediately. The most serious item is an unauthenticated privilege escalation through Template Part block attributes that, according to the WordPress 7.1.5 release post on WordPress.org News, could lead to remote code execution. Sites with automatic background updates should receive 7.1.5 on their own. Sites without them need a manual update from the Dashboard.
What WordPress released on 18 November 2026
The release post, published on 18 November 2026 by Jeremy Felt in the Releases and Security categories, describes 7.1.5 as a short-cycle release that "features fixes for multiple issues." It gives two ways to update: download WordPress 7.1.5 from WordPress.org, or open the WordPress Dashboard, click "Updates" and then "Update Now." It adds that sites supporting automatic background updates will start the update process automatically.
The post lists 20 security items. Eighteen are vulnerabilities. Two are described as hardening changes: a fix to a malformed regular expression that broadened JSON media type matching, and the removal of the block editor's Imgur embed variation, whose server-side provider the post says is already gone. The release was led by Jeremy Felt, Jerry Jones and Jarda Snajdr.
WordPress.org also said that WordPress 7.2 Release Candidate 2 has been released with all applicable fixes, and that the next major release, WordPress 7.2, is currently planned for 8 December 2026.
The 20 fixes, grouped by the access an attacker needs
The release post labels most items with the lowest user role that can exploit them, using WordPress's "Role+" convention (Author+ means an Author or any role above it). The table below groups all 20 items by that label. Where the post gives no role, the table says so rather than guessing.
| Access needed (as labelled by WordPress.org) | Fixes in WordPress 7.1.5 |
|---|---|
| Unauthenticated (no login) | Privilege escalation via Template Part block attributes that could lead to remote code execution; stored XSS via shortcode attributes in comments; disclosure of private taxonomy terms via the REST API search endpoint; denial of service via batched XML-RPC pingbacks |
| Subscriber+ | Information disclosure via XML-RPC wp.getComments |
| Contributor+ | XSS via scripts in oEmbed provider responses; stored XSS in the Comment Date block via its date format; stored XSS in the block editor via media filenames when converting a media block to a File block |
| Author+ | Exposure of user email addresses via the REST API comments endpoint; authorization bypass via comment editing in the admin |
| Editor+ | Information disclosure via post and template author assignment in the REST API |
| Administrator | Multisite privilege escalation letting a site Administrator take over a Super Admin account via Customizer menu previews; stored XSS via Customizer previews |
| Role not stated | Reflected XSS in the legacy media library popup; XSS in wp_interactivity_data_wp_context() via the store namespace; SQL injection in WP_Meta_Query via nested relation values; SQL injection via the front page setting in Customizer changeset previews; XSS in the block editor via Openverse image metadata |
| Hardening (not a vulnerability) | Corrected regular expression for JSON media type matching; removal of the Imgur embed variation |
The four issues that need no login
Four of the 20 items carry the "unauthenticated" label, which means the post describes them as exploitable by someone with no account on the site. The Template Part privilege escalation, reported by Logan Homolka, is the one WordPress.org says could lead to remote code execution. Remote code execution on a web server generally means an attacker can run their own code there, which is the usual path to a full site takeover.
The second is stored cross-site scripting through shortcode attributes in comments. Stored XSS means a malicious script is saved on the site and runs later in other visitors' browsers. Because comments are often open to anyone, this one is relevant to blogs and news sites that accept public comments. The third is a disclosure of private taxonomy terms through the REST API search endpoint. The fourth is a denial of service through batched XML-RPC pingbacks, which concerns availability rather than data.
The release post does not give technical detail, proof-of-concept code or exploit conditions for any of these. That is normal for a WordPress security release, and it is a reason to update before such details become public.
Issues that need a logged-in account
Nine items need some level of login, from Subscriber up to Administrator. These matter most on sites that hand out accounts: membership sites, sites with open registration, multi-author blogs, agencies or freelancers with editor access, and WordPress multisite networks. The multisite issue is the clearest example. According to the release post, a site Administrator on a network could take over a Super Admin account through Customizer menu previews, which would let a single compromised sub-site reach the whole network.
Older WordPress versions and the backports
WordPress.org said the security fixes were backported "as a courtesy" to all branches still eligible for security fixes, which it gave as currently reaching back to version 4.7. It also said the backports are still in progress and will ship as they become ready, so an older branch may not have its patched release yet. The post repeats that only the most recent version of WordPress is actively supported.
One more change is bundled with the backports. WordPress 7.0 removed 1024-bit certificates from its bundled root certificates, and WordPress.org said this change has now been applied to 6.9.12 and earlier as part of this release.
Who updates automatically, and who does not
This section is analysis, not part of the release post. WordPress.org says automatic background updates will start on sites that support them, but it does not say which sites those are. In practice, minor and security releases are applied automatically by default in WordPress core, and several things can stop that from happening:
- A wp-config.php setting such as AUTOMATIC_UPDATER_DISABLED or WP_AUTO_UPDATE_CORE set to false.
- A WordPress install managed through version control, where core files are deployed from a repository rather than updated in place.
- A hosting control panel or managed host that runs its own update schedule and may hold releases for testing.
- File permission problems that prevent WordPress from writing new core files.
- Very old sites on a branch whose backport has not shipped yet.
If any of these apply, the safe assumption is that the site has not updated until someone has checked the version number.
What to check on your WordPress sites this week
The following steps are a practical checklist, not instructions from WordPress.org.
- Confirm the version. In the Dashboard, the "At a Glance" widget and the Updates screen show the running version. Sites on the 7.1 branch should show 7.1.5.
- Update anything that has not moved, starting with sites that allow public comments or open registration, since two of the unauthenticated issues touch comments and the REST API.
- For sites on older branches, check whether a patched release for that branch has shipped, because WordPress.org says the backports are still in progress. Treat this as a reason to plan an upgrade to the current version.
- Review user accounts. Remove stale Contributor, Author and Editor accounts, since nine of the fixes need a logged-in role.
- On multisite networks, review who holds site Administrator and Super Admin roles, given the Customizer menu preview issue.
- If the site does not use XML-RPC, consider whether it needs to stay reachable, since two fixes involve XML-RPC.
- Take a backup before updating, and keep it after, so a clean copy exists if anything looks wrong later.
Why a core security release matters for marketing sites
This section is analysis. A hacked WordPress site is a marketing problem as well as an IT problem. Compromised sites are commonly used to inject spam pages, hidden links or redirects, and Google can flag them in Search Console's Security issues report and show warnings to searchers. Recovery takes time: the site has to be cleaned, the cause closed, and a review requested before warnings are removed. For a business whose leads come through its website, that can mean weeks of lost organic traffic and wasted paid clicks landing on a flagged page.
A remote code execution path in WordPress core is the kind of issue that makes this scenario more likely, because core runs on every WordPress site regardless of theme or plugins. Updating quickly is cheaper than cleaning up. A regular SEO audit that includes a security and index check is one way to catch injected pages early if something does get through.
What the release post did not say
The WordPress.org post is short, and several things readers may want are missing from it:
- It does not say whether any of the 20 issues have been exploited in the wild.
- It does not publish CVE identifiers or severity scores.
- It does not say which WordPress versions each issue affects.
- It does not list the exact backport release numbers for older branches, only that backports are in progress.
- It does not mention plugins or themes. Plugin vulnerabilities are a separate risk and are not covered by a core update.
- It does not mention any specific country or region.
Where this article describes impact or gives a checklist, that is analysis based on how WordPress works, not a statement from WordPress.org.
What this means for Thai marketers
The release post does not mention Thailand. The relevance is practical: WordPress is a common platform for company websites, blogs and small online stores, and many of those sites are built once and then left with whoever set up the hosting. Those are the sites most likely to miss an update. If your business site runs WordPress, ask whoever manages it to confirm the version is 7.1.5 (or a patched backport) and to check that automatic minor updates are on.
If the site is old, on an unsupported branch, or nobody is sure who maintains it, that is a signal to plan a proper rebuild or a maintenance arrangement. A web design project is a good moment to fix update settings, hosting access and user roles at the same time, and to make sure the site's SEO is not lost in the move.
Frequently asked questions about WordPress 7.1.5
Do I need to update to WordPress 7.1.5 right away?
Yes, WordPress.org recommends updating immediately because 7.1.5 is a security release. Sites with automatic background updates should get it on their own, but it is worth confirming the version number in the Dashboard rather than assuming.
What is the most serious vulnerability fixed in WordPress 7.1.5?
The most serious is an unauthenticated privilege escalation through Template Part block attributes that WordPress.org says could lead to remote code execution. It was reported by Logan Homolka. The release post gives no further technical detail.
My site runs an older version of WordPress. Is it patched?
Possibly not yet. WordPress.org says the fixes were backported to all branches eligible for security fixes, currently back to 4.7, but that the backports are still in progress and will ship as they become ready. Only the latest version is actively supported.
Does WordPress 7.2 include these fixes?
Yes, WordPress.org says WordPress 7.2 RC 2 has been released with all applicable fixes. The final WordPress 7.2 release is currently planned for 8 December 2026.
Have these WordPress vulnerabilities been exploited?
Not stated. The release post does not say whether any of the 20 issues have been used in attacks, and it does not publish CVE numbers.
Next steps
WordPress 7.1.5 is a quick update for most sites and an easy one to miss on sites nobody watches. Check the version on every WordPress property you own, clear out unused accounts, and confirm that automatic minor updates are switched on. If your site needs a rebuild or a safer setup, Relevant Audience can help with that work.







