
On November 18, WordPress released 7.1.5, a security-only update. WordPress counts 18 vulnerabilities plus two hardening changes; Wordfence counts 19. The exact number matters less than one detail: some of these flaws can be exploited by someone who has never logged into your site.
If your dashboard still shows an update waiting, this article is your checkup.
The symptoms: what 7.1.5 treats
1. Unauthenticated privilege escalation (the critical one). The Template Part block, which powers headers and footers, could be abused by a visitor with no account to gain permissions. WordPress says this could lead to remote code execution, meaning an attacker running code on your server.
2. Multisite Super Admin takeover. On Multisite networks, the admin of one sub-site could seize the Super Admin account through Customizer menu previews.
3. Two SQL injections and several stored XSS flaws. Classic attack paths for stealing data or planting malicious scripts in your pages.
4. Information leaks. Private categories and tags were searchable through the REST API without logging in. Author-level users could see other users’ email addresses.
Patches were also backported to every supported branch down to 4.7.
The diagnosis: why this keeps happening
7.1.5 is the fifth security release since WordPress 7.1 launched on August 19:
| Release | Date | Security fixes |
|---|---|---|
| 7.1.1 | Sept 17 | 11 |
| 7.1.2 | Sept 22 | 1 (unauthenticated file inclusion, possible RCE) |
| 7.1.3 | Oct 6 | 7 |
| 7.1.4 | Oct 28 | 22 |
| 7.1.5 | Nov 18 | 18 + 2 hardening |
That’s more than 60 core fixes in about 13 weeks. Researchers armed with AI tools are finding flaws faster than ever, and every public patch tells attackers exactly where to look on sites that haven’t updated.
Exposure is wide. At the end of October, about 35.6% of WordPress installs were still running a branch older than 7.1 (WordPress.org data via WebHosting.Today).
The prognosis if you wait
A compromised WordPress site rarely just “goes down.” The usual complications:
- Search penalties: “This site may be hacked” warnings in Google and Chrome’s red “Deceptive site ahead” screen.
- SEO contamination: thousands of injected spam pages that drag your real rankings down.
- Ad shutdown: Google Ads disapproves ads pointing to compromised sites.
- Email blacklisting: your domain lands on spam blocklists, and invoices stop reaching clients.
- Ransomware: files and databases encrypted, with payment demanded in crypto. Small businesses pay thousands, and recovery often costs even more.
- Legal exposure: leaked customer data can trigger breach-reporting obligations under PIPEDA, and under Law 25 in Quebec.
Cleanup takes days. Winning back Google’s trust can take months. Already seeing symptoms? Go straight to our hacked WordPress site emergency page.
The treatment plan
- Patch now. Update to 7.1.5 or the latest release on your branch.
- Verify auto-updates. Minor security updates are on by default, but hosts and plugins sometimes disable them.
- Weekly plugin and theme updates. Most WordPress vulnerabilities live there, not in core.
- Off-site backups, tested. If you’ve never restored one, you don’t have a backup plan.
- Stage before you update. Big updates go to a staging copy first.
- Firewall and monitoring. Block known attacks and get alerts on file changes.
- Remove dead weight. Unused plugins, inactive themes and old admin accounts are open doors.
Rather not handle this yourself? Our Care Plans take care of updates, backups and monitoring for you.
Get a free checkup
Not sure which version you’re running, or what’s hiding in your plugins? Get a free WP Doctor™ check-up. No plugin to install and no login required. In minutes, you’ll see your WordPress version, outdated components and known vulnerabilities, with a clear priority list of what to fix first.
WP Doctor™ is a Novium Systems™ service.
Sources: Wordfence, Search Engine Journal, WebHosting.Today.