WordPress 7.1.5 is a security release, and site owners should update immediately.
- 19 distinct vulnerabilities are tracked by Wordfence, including one Critical and four High-severity issues based on CVSS v3.1.
- Notable issues include an unauthenticated privilege escalation that could lead to remote code execution, SQL injection, stored cross-site scripting, XML-RPC denial of service, and a multisite Administrator-to-Super-Administrator privilege escalation.
- Eight vulnerabilities do not require authentication to exploit. However, several have additional prerequisites or require user interaction, so they are not universally exploitable on every WordPress site.
WordPress 7.1.5 was released on November 18, 2026, with fixes for a broad group of security issues affecting WordPress Core. The release addresses privilege escalation, cross-site scripting, SQL injection, information disclosure, authorization bypass, cross-site request forgery, and denial of service.
WordPress recommends updating immediately. Most sites with automatic background updates enabled will begin receiving the release automatically, but site owners should still confirm that the update completed. Go to Dashboard > Updates and verify that the site is running WordPress 7.1.5 or the corresponding fixed release for its branch.
WordPress 7.1.5 fixes several consequential vulnerabilities. According to WordPress, the Template Part block attribute issue is an unauthenticated privilege escalation that could lead to remote code execution. The release also addresses a Critical privilege escalation on multisite, multiple cross-site scripting vulnerabilities, two SQL injection vulnerabilities, information disclosure, authorization bypass, and denial of service.
WordPress 7.1.5 at a Glance
Why Wordfence counts 19 vulnerabilities
The official WordPress announcement contains 20 security bullets. Two are expressly described as hardening changes rather than vulnerabilities: a correction to JSON media-type matching and removal of an obsolete Imgur embed variation. That leaves 18 vulnerability bullets.
One of those bullets, the authorization bypass in admin comment editing, contains two distinct vulnerabilities. One lets an Author move an approved comment to another user’s post; the other lets an Author change a private editorial Note into a public comment. They have different attacker-controlled fields, impacts, and affected version ranges, so Wordfence tracks them separately. The result is 19 vulnerability records and two hardening changes.
The Most Significant Vulnerabilities
Multisite Administrator to Super Administrator Privilege Escalation
The highest-scoring issue, with a CVSS v3.1 score of 9.1 (Critical), affects WordPress multisite. According to WordPress, a site-level Administrator can abuse Customizer navigation-menu preview handling to cross the network-administration boundary and take over a Super Administrator account.
This issue requires an authenticated site Administrator and a multisite installation. It does not give an unauthenticated visitor Administrator access, and on a standard single-site installation an Administrator already holds the site’s highest ordinary role. WordPress 7.1.5 separates the security context used to validate navigation-menu preview arguments, preventing the cross-context reuse at the center of the vulnerability.
Unauthenticated Privilege Escalation via Template Part Block Attributes
The WordPress announcement describes this issue as an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. The Wordfence Intelligence record classifies the issue as client-side cross-site request forgery leading to Administrator account creation and assigns it a CVSS v3.1 score of 8.8 (High).
Unauthenticated Stored XSS Through Shortcode Attributes in Comments
WordPress describes this issue as unauthenticated stored cross-site scripting through shortcode attributes in comments. It can allow an attacker without an account to inject a malicious web script into comment content that executes when the affected content is viewed.
SQL Injection and XML-RPC Denial of Service
Two other unauthenticated issues carry CVSS v3.1 scores of 7.5 (High). The first is SQL injection through nested WP_Meta_Query relation values, which can allow an attacker to alter database queries and access sensitive information.
The second allows unauthenticated clients to batch multiple pingback.ping calls inside one XML-RPC system.multicall request. Each pingback can trigger database and network work, allowing repeated requests to multiply server load. The path requires XML-RPC to be reachable. WordPress 7.1.5 limits each XML-RPC request to one pingback.
All 19 Vulnerabilities at a Glance
The table below uses practical attacker access rather than treating every issue as equally exposed. CVSS v3.1 and CVSS v4.0 scores are shown because the two standards model impact differently. Each vulnerability name links to its full Wordfence Intelligence record.
| Vulnerability | Attacker access | Primary impact | CVSS v3.1 / v4.0 |
|---|---|---|---|
| No attacker authentication required — 8 vulnerabilities | |||
| Legacy media popup reflected XSS | Unauthenticated | Reflected script execution through the legacy media library popup. | 4.7 v3.1 7.5 v4.0 |
| Interactivity API store-namespace XSS | Unauthenticated | Script execution through the Interactivity API store namespace. | 4.7 v3.1 7.5 v4.0 |
Nested WP_Meta_Query relation SQL injection |
Unauthenticated | SQL injection through nested WP_Meta_Query relation values. |
7.5 v3.1 8.7 v4.0 |
| Private taxonomy term disclosure through REST search | Unauthenticated | Disclosure of private taxonomy term names. | 5.3 v3.1 6.9 v4.0 |
| Stored XSS through shortcode attributes in comments | Unauthenticated | Stored script execution through shortcode attributes in comments. | 7.2 v3.1 8.7 v4.0 |
| Batched XML-RPC pingback denial of service | Unauthenticated | Resource exhaustion by multiplying pingback work in one XML-RPC request. | 7.5 v3.1 8.7 v4.0 |
| Template Part block attribute privilege escalation | Unauthenticated | Privilege escalation that could lead to remote code execution. | 8.8 v3.1 8.6 v4.0 |
| Stored XSS through Openverse image metadata | Unauthenticated | Cross-site scripting in the block editor through Openverse image metadata. | 5.4 v3.1 7.7 v4.0 |
| Subscriber or Contributor access — 4 vulnerabilities | |||
| Private comment disclosure through XML-RPC | Subscriber+ | Disclosure of private comment content and commenter email and IP address. | 4.3 v3.1 5.3 v4.0 |
| Stored XSS through oEmbed provider scripts | Contributor+ | Script execution in a privileged editor through a Contributor-controlled oEmbed provider. | 6.4 v3.1 8.6 v4.0 |
| Stored XSS through Comment Date format | Contributor+ | Stored script execution through the block’s date-format value. | 6.4 v3.1 8.6 v4.0 |
| Stored XSS through a File transform filename | Contributor+ | Stored script execution through a media filename when converting a media block to a File block. | 6.4 v3.1 8.6 v4.0 |
| Author or Editor access — 4 vulnerabilities | |||
| User email disclosure through REST comment editing | Author+ | Disclosure of a user’s current email address through comment-author refresh behavior. | 4.3 v3.1 5.3 v4.0 |
| Unauthorized comment move through admin editing | Author+ | Moving an approved comment to another user’s post without permission. | 4.3 v3.1 5.3 v4.0 |
| Private Note publication through comment-type change | Author+ | Publication of a private editorial Note as a public comment. | 5.4 v3.1 5.3 v4.0 |
| Network user enumeration through REST author assignment | Editor+ | Account-existence disclosure across a multisite network. | 2.7 v3.1 5.1 v4.0 |
| Administrator access — 3 vulnerabilities | |||
| Multisite Super Administrator privilege escalation | Administrator+ | Takeover of a Super Administrator account on multisite. | 9.1 v3.1 8.6 v4.0 |
| Customizer front-page preview SQL injection | Administrator+ | Database information disclosure through a crafted Customizer preview value. | 4.9 v3.1 6.9 v4.0 |
| Stored XSS through Customizer previews | Administrator+ | Stored script execution when a victim opens a crafted Customizer preview. | 4.4 v3.1 4.8 v4.0 |
No CVE identifiers were listed for these vulnerabilities in the public advisories at the time of publication. The linked Wordfence Intelligence records contain affected version ranges, fixed versions, CVSS vectors, technical descriptions, and researcher attribution.
Two Additional Hardening Changes
WordPress also included two changes that we do not treat as separate vulnerability records:
- JSON media-type matching: WordPress corrected a malformed regular expression that could match a broader range of media types than intended. The WordPress Security Team described this as hardening, and the public material does not identify a distinct exploit.
- Imgur embed variation: WordPress removed an obsolete block-editor variation for Imgur after its server-side provider had already been discontinued. This is also described as hardening rather than a newly disclosed vulnerability.
What WordPress Site Owners Should Do
- Update WordPress immediately. Install WordPress 7.1.5 or the fixed security release for your current eligible branch. The official WordPress 7.1.5 documentation lists every backported release.
- Verify that the update completed. Do not assume an automatic update succeeded. Check Dashboard > Updates on every site you manage.
- Upgrade unsupported branches. WordPress 4.6 and earlier no longer receive security updates. WordPress also notes that only the latest release is actively supported; older security backports are provided as a courtesy.
- Review who has publishing and administrative access. Several vulnerabilities require Contributor, Author, Editor, or Administrator privileges. Remove unused accounts and keep each user at the lowest role they need.
- Run a Wordfence scan after updating. A scan can verify Core file integrity and identify unexpected changes or malicious files that need investigation.
Conclusion
WordPress 7.1.5 fixes 19 distinct vulnerabilities tracked by Wordfence, ranging from a Critical multisite privilege escalation and an unauthenticated privilege escalation that could lead to remote code execution to cross-site scripting, SQL injection, denial of service, authorization bypass, and information disclosure. Eight of the vulnerabilities are unauthenticated.
The absence of a single universal exploit path does not make the release optional. The strongest protection is to remove the vulnerable behavior by updating WordPress Core. Confirm that every site is running WordPress 7.1.5 or the appropriate backport, and move sites on WordPress 4.6 or earlier to a supported release.
We thank the WordPress Security Team and the researchers credited for these fixes: Mo Jangda, Yuval Miller, Anthropic, Juliette Reinders Folmer, Christiaan Swiers, Ben Bidner, Rudy Faile, vvh1te3zz, Rafie Muhammad, Giovanni Cintolo, Jarda Snajdr, Weston Ruter, Jesse McNeil, Jaewook Lee, Zhengyu Liu, Jingcheng Yang, Gavin Zhong, Jeremy Felt, Logan Homolka, Shu Takahashi, and CryptoFox.
Sources
- WordPress 7.1.5 release announcement
- WordPress 7.1.5 version and backport documentation
- Wordfence Intelligence: WordPress Core vulnerabilities
Sign up for the Wordfence mailing list to receive important WordPress security news and vulnerability reports as soon as they are published.
The post WordPress 7.1.5 Security Release Fixes 19 Vulnerabilities appeared first on Wordfence.