WordPress 7.1.5 security release is out: 20 security fixes are listed
WordPress.org released the 7.1.5 security update on November 18, 2026. Its release notes list 20 items and advise sites to update right away. Sites that support automatic background updates install it on their own. The next major version, 7.2, is planned for December 8.
WordPress.org shipped 7.1.5 as a security release
A post on the WordPress.org news site dated November 18, 2026 calls 7.1.5 a security release that closes several issues. Because it is a security update, the post says sites should not wait. You can install it from the Updates screen in the WordPress dashboard, and sites that support automatic background updates will begin installing it without any action.
The release is described as a short-cycle one. The next major version, 7.2, has a planned launch of December 8. Its first release candidate (RC1) came out the day before 7.1.5, on November 17, 2026, and the 7.1.5 post adds that a second candidate (RC 2) has also been published with the applicable fixes.
The fixes range from SQL injection and XSS to privilege escalation and denial of service
The release notes count 20 security items. Below we summarize only the headline entries in our own words; for the full list, read the source.
Privilege problems: on multisite installs, a flaw was closed that allowed an Administrator of a single site to seize the network's Super Admin account by way of Customizer menu previews. Another item covers privilege escalation by an unauthenticated visitor through Template Part block attributes, which the post says could lead to remote code execution. An authorization bypass for Author-level users and above, via comment editing in the admin, is on the list as well.
Injection and XSS: two separate SQL injection paths were fixed, one through nested relation values in WP_Meta_Query and one through the front page setting in Customizer changeset previews. The XSS entries touch the legacy media library popup, the Interactivity API context, oEmbed responses, Customizer previews, the Comment Date block's date format, Openverse image data in the block editor and media filenames. One of them is an unauthenticated stored XSS reached through shortcode attributes in comments.
Information leaks and service disruption: fixes cover private taxonomy terms exposed by the REST API search endpoint, user email addresses exposed by the REST comments endpoint, and data exposed through the XML-RPC wp.getComments method. Batched XML-RPC pingbacks that could knock a site over without authentication are also listed. The post credits two of the reports (the legacy media popup XSS and the REST taxonomy leak) to Anthropic, and the others to WordPress Security Team members and other named researchers.
Backports: the post says the security fixes were backported to every branch still eligible for them, currently reaching back to 4.7, that this work is in progress, and that each branch ships when ready. It also reminds readers that only the newest WordPress version is actively supported. Separately, the removal of 1024 bit certificates from the bundled root certificates, made in 7.0, has now been applied to 6.9.12 and earlier.
Some of the items do not even require a login
Several listed items are described as reachable without authentication, while others need a particular user role (for example Contributor and above, or Author and above). That distinction matters differently by site type: sites with open comments, multi-author sites and multisite networks line up with different entries on the list. That inference is ours, since the post does not rank which kind of site is most exposed.
The second point is update habits. The post says sites that support automatic background updates will start the install on their own. For sites where that feature was switched off, or where an agency or host manages updates, it falls to the owner to confirm the new version actually landed.
The third point is the 7.2 timeline. RC1 was announced as a test build that should not run on production or mission-critical sites; WordPress.org points people to a separate test server instead. The RC1 post lists bug fixes, accessibility work, a skip link in the admin bar and client-side media upload fixes, and it asks plugin and theme authors to wrap up their testing with RC1 and set the "Tested up to" field in their readme to 7.2 ahead of the December 8 target.
What it means for businesses in Türkiye
This section is our reading, not a fact from the sources. The WordPress.org announcement is about a software release, so corporate sites, blogs and online stores in Türkiye that run WordPress should apply the same update.
The practical steps are our suggestions too: check in the dashboard that the version reads 7.1.5, ask your host or agency whether automatic updates were turned off, and take a backup before updating. If you run a multisite network or keep comments open, it makes sense to move that check up the list. Try 7.2 RC1 only in a separate test environment.
The UNALSOFT view
Security releases are a reminder that WordPress upkeep comes down to three plain questions: who watches for updates, whether automatic updates are on, and where the backup sits. We read this news as a prompt for site owners to review their own maintenance routine. In web design projects we see these as topics to settle before a site goes live.
Is your WordPress site up to date, and who is watching the updates?
A short conversation is enough to review your site's maintenance and update routine together.