The short answer
WordPress 7.1.5 came out on November 18, 2026, and the WordPress project says to update immediately. Wordfence counts 19 distinct vulnerabilities in the release, one rated Critical and four rated High, and 8 of them can be triggered without logging in. The most serious issues let a site Administrator on a multisite network take over the Super Admin account, and let an outside attacker create a new Administrator if a real Administrator clicks a crafted link. Most sites with automatic background updates will get the fix on their own, but do not assume it worked: open Dashboard, then Updates, and confirm the site says 7.1.5 (or the fixed release for your older branch). If you run WordPress multisite, accept comments, or leave XML-RPC on, treat this one as urgent.
What was released
The WordPress 7.1.5 announcement calls it a security release and says, "it is recommended that you update your sites immediately." It lists 20 security items. Wordfence explains that two of them are hardening changes rather than vulnerabilities, and that one item covers two separate bugs, which is how it arrives at 19 distinct vulnerabilities. By Wordfence’s count, 8 require no login, 8 are cross-site scripting issues, and the scores (CVSS 3.1) include one Critical and four High.
The fixes were backported to every branch that still gets security updates, which the WordPress project says currently goes back to 4.7. The announcement notes those backports "are in progress and will ship as they become ready," and that only the latest version is actively supported. WordPress 7.2 RC 2 shipped with the same fixes, and 7.2 itself is planned for December 8.
Two of the 20 items were credited to Anthropic, the AI company, alongside independent researchers and the WordPress Security Team. That is a small sign of where security research is heading: AI tools are finding real bugs in widely used software, which means fixes will keep arriving and staying current matters more.
The five most serious issues
Scores below are the CVSS 3.1 ratings from Wordfence. The middle column is what an attacker needs, which matters more for a small business than the score.
| Issue | What an attacker needs | Score |
|---|---|---|
| Multisite Administrator to Super Admin takeover (Customizer menu previews) | Site Administrator on a multisite network | 9.1 Critical |
| Template Part block attributes: crafted site-editor link creates a new Administrator | No login, but an Administrator has to open the link | 8.8 High |
| SQL injection through nested WP_Meta_Query relation values | No login | 7.5 High |
| XML-RPC denial of service through batched pingbacks | No login, XML-RPC reachable | 7.5 High |
| Stored cross-site scripting through shortcode attributes in comments | No login, comment must be approved and shown | 7.2 High |
A few details from the Wordfence write-up help put these in context:
- The Critical one only matters on multisite. On a normal single site, the Administrator already has the top ordinary role, so there is nothing higher to take over.
- The Template Part issue needs a click. WordPress describes it as an unauthenticated privilege escalation that "could lead to remote code execution." Wordfence says the path it proved requires an Administrator to open a crafted site-editor link, after which a new attacker-chosen Administrator account was created on 7.1.4. Remote code execution was not demonstrated.
- The comment issue needs approval. The malicious comment has to be approved and displayed before the script runs.
- The XML-RPC issue is about load. One request could bundle many pingbacks and multiply the work your server does. 7.1.5 limits each request to one pingback.
Wordfence also notes that no CVE numbers had been listed for these issues when it published on November 19. Neither post reports active exploitation, and none of these issues appear in the CISA Known Exploited Vulnerabilities catalog as of its November 18 update. That is not a reason to wait. Once fixes are public, attackers can compare the old and new code to work out how to exploit them.
What to do this week
1. Confirm the version on every site
Log in, open Dashboard, then Updates, and check that it says WordPress 7.1.5. Wordfence’s advice is blunt: "Do not assume an automatic update succeeded." If you are on an older branch on purpose, the fixed releases include 7.0.9, 6.9.12, 6.8.13 and so on back to 4.7.40, according to Wordfence. Sites on 4.6 or earlier get no security updates at all.
2. Back up, then update
If the update has not run, take a backup first and then click Update Now. If you are on managed WordPress hosting, ask your host to confirm in writing that 7.1.5 is applied to your site.
3. Multisite networks go first
If you run a network of sites, the Critical issue means any site Administrator could have become a Super Admin. After updating, review the list of Super Admins and remove anyone you do not recognize.
4. Tighten who can publish
Several of the 19 issues need a Contributor, Author or Editor account. Remove old accounts, keep each person at the lowest role they need, and turn on multi-factor sign-in for Administrators.
5. Turn off what you do not use
If nothing on your site depends on XML-RPC (some older apps and plugins do), turning it off removes a common attack target. If you do not want comments, close them. If you keep them, keep moderation on.
6. Be careful with links to your own admin
Remind anyone with Administrator access not to click unexpected links into the site editor, even ones that look like they point to your own site.
7. Scan after updating
Run a file-integrity or malware scan after the update to catch anything that changed before the patch went in.
What it means for a small business
This is the second WordPress core security release in about three weeks. WordPress 7.1.4 shipped on October 28 to fix CVE-2026-119977, which CISA added to its exploited list on November 3 (our coverage). Core releases like this are routine for a well-run site and painful for a neglected one. If nobody on your team owns updates, or you are not sure what version you are on, that is the real risk. A short monthly check (version, plugins, users, backups) prevents most of the emergencies we see.
FAQ
What does WordPress 7.1.5 fix?
It is a security release from November 18, 2026. Wordfence counts 19 distinct vulnerabilities, including a Critical multisite privilege escalation, a crafted-link issue that can create a new Administrator, SQL injection, stored cross-site scripting, and an XML-RPC denial of service.
Is WordPress 7.1.5 an urgent update?
Yes. The WordPress project recommends updating immediately. Eight of the 19 vulnerabilities can be triggered without logging in, though several need extra conditions such as an approved comment or an Administrator clicking a link.
How do I check if my site has WordPress 7.1.5?
Log in and go to Dashboard, then Updates. It should say you have WordPress 7.1.5, or the fixed release for your branch, such as 7.0.9 or 6.9.12. Do not assume an automatic update completed.
Are these WordPress 7.1.5 vulnerabilities being exploited?
Neither the WordPress announcement nor Wordfence's November 19 analysis reported active exploitation, and none were in CISA's Known Exploited Vulnerabilities catalog as of November 18, 2026. Patching now is still the safe choice.
I am on an older WordPress version. Do I get the fix?
Security fixes were backported to branches back to 4.7, and the WordPress project says those backports ship as they become ready. Sites on 4.6 or earlier get no security updates and should be upgraded.
Does my host install WordPress 7.1.5 for me?
Many managed hosts and sites with automatic background updates will get it automatically. Ask your host to confirm it was applied, and check the version yourself.
Sources
- WordPress.org, "WordPress 7.1.5 Release" (November 18, 2026). https://wordpress.org/news/2026/11/wordpress-7-1-5-release/
- Wordfence, "WordPress 7.1.5 Security Release Fixes 19 Vulnerabilities" (November 19, 2026). https://www.wordfence.com/blog/2026/11/wordpress-7-1-5-security-release-fixes-19-vulnerabilities/
- CISA, Known Exploited Vulnerabilities Catalog (checked against the November 18, 2026 release). https://www.cisa.gov/known-exploited-vulnerabilities-catalog