WordPress released version 7.1.5 on 18 November 2026, a security update addressing authorization problems, SQL injection, cross-site scripting and information disclosure. The project recommends updating websites immediately. For businesses using WordPress, the release concerns application protection and the continuity of commercial functions: forms, accounts, content administration and, where applicable, online store orders. Version 7.1.5 is a maintenance release. WordPress 7.2 is on a separate release-candidate track, rather than being the stable version businesses are being asked to install through this announcement.
The fixes cover several WordPress components
The list published by WordPress covers the administration interface, block editor, Customizer, REST API, comments and XML-RPC. These components serve different purposes: some are used by website editors, while others support connected applications or visitor interactions. The update therefore goes beyond a visible design change. It changes how the core validates information, controls access and handles particular requests across several parts of the application.
One reported issue is an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. The announcement also includes SQL injection involving values in WP_Meta_Query and Customizer previews. This identifies the areas being repaired. The release announcement does not establish that every website has been exploited or that every installation and configuration has the same exposure to each issue.
The release also fixes cross-site scripting, or XSS: situations in which improperly handled data can introduce scripts into a page context. The published examples involve the legacy media library, responses from oEmbed providers, shortcode attributes in comments, Openverse image metadata and conversions between media blocks. The common response is to update the code processing those inputs, rather than indiscriminately removing the website's existing content.
From release announcement to a confirmed update
- Identify
Installed version and active components
- Prepare
Backup and extension compatibility
- Update
Available package for the installed branch
- Confirm
Version, forms, accounts and orders

User permissions matter when assessing exposure
For several issues, WordPress specifies the minimum role involved: Subscriber, Contributor, Author, Editor or Administrator. A vulnerability reachable without an account has different conditions from one requiring an authenticated editorial user. This distinction helps the technical team interpret the announcement and review administration access. The existence of a user account alone is not evidence that an incident has taken place on that website.
Multisite installations have a separately described issue in which a site Administrator could take over a Super Admin account through Customizer menu previews. Multisite means running a network of websites within a single WordPress installation. The separation between a site's administrator and the administrator of the whole network explains why this correction concerns an important authorization boundary, particularly for businesses managing several related websites.
The information-disclosure issues described in the announcement include private taxonomy terms and user email addresses under the technical conditions listed for each problem. There is also a denial-of-service fix involving batched XML-RPC pingback requests. Websites using external integrations need to be assessed against their actual components and configuration, with a record of installed versions and the security update applied to the installation.
Version 7.1.5, older branches and WordPress 7.2 RC2
Version 7.1.5 is published as a short-cycle security release. The same announcement says the fixes are being backported to branches eligible for security corrections, currently reaching back to 4.7. Those backports are in progress, and packages ship as they become ready. An administrator therefore checks the update actually available for the installed branch, rather than assuming every branch received its package at exactly the same time.
WordPress states that only its most recent version is actively supported. Providing certain security corrections for older branches does not mean they receive ongoing development on the same terms. For an older commercial website, applying a security correction and planning a move to a current version are separate activities. The latter requires checking the theme, extensions and any custom code against the intended target version.
WordPress 7.2 RC2 has also been released with applicable fixes, while the final 7.2 release is planned for 8 December 2026. RC means release candidate, used to check the upcoming version. Its appearance in this announcement does not alter the stable status of 7.1.5. Businesses should not read it as an instruction to move their production website directly onto a release that is still being prepared.
Release status on 20 November 2026
| Version | Status | Relevant detail |
|---|---|---|
| 7.1.5 | Released | Security update dated 18 November |
| Eligible older branches | Backports in progress | Packages ship as they become ready |
| 7.2 RC2 | Release candidate | Includes applicable fixes |
| 7.2 final | Planned | 8 December 2026 |
Updating includes checking the website's functions
WordPress distributes the release through the normal administration update mechanism, and websites supporting automatic background updates can receive it automatically. A WordPress maintenance process tracks both the installation and its outcome. This includes confirming the active version and the functions used by the business. Having the automatic-update option enabled is a configuration detail; the completed installation and subsequent checks provide the operational record.
WordPress documentation recommends backing up before updating and checking theme and plugin compatibility. Website recovery depends on both files and the database. After the update, checks should cover the functions the business relies on: authentication, forms, page publishing and existing order workflows. The checks are adapted to the particular website, without adding unrelated components solely because a new security release has become available.
Core fixes do not automatically update every commercial extension or describe the condition of each custom integration. Within a web security service, version records, backups and functional checks remain complementary activities. For a business owner, the essential information is the WordPress version in use and confirmation that the appropriate update was applied, with a designated technical owner and a clear record of the work carried out.
The official documentation also describes the temporary maintenance mode used during an update. That is a stage in the operation, rather than confirmation that the entire process has finished. The same documentation pairs checking the website after installation with reviewing any remaining theme and plugin updates. Separating these steps provides a more precise record than simply observing an update notification in the administration dashboard.