WordPress 7.1.2 shipped on 22 September 2026. The first attack attempt arrived before lunch the same day. By the next morning, ready-made scanning tools were circulating and attack traffic was ten times what it had been that first evening (Patchstack).
The reason is CVE-2026-87902, a flaw in WordPress core itself, not in a plugin or theme. On a site that meets the right conditions, someone with no account and no password can get your server to run their commands. Every WordPress release since 4.7 is affected.
The short version: if you are not on 7.1.2 (or the patched release for your branch, listed below), update today. Read on for what actually goes wrong, which sites are most exposed, how to check yours, and what to look for once you have patched.
What goes wrong
When WordPress renders a page, it picks the template file based on the page's name. For a page called "about", it checks whether the theme has a page-about.php. That name comes from the incoming request, so WordPress cleans it first.
The cleaning is where it breaks. If the name contains ../ (“go up one folder”) written plainly, the filter strips it. Written in encoded form, it slips through, and reappears when WordPress decodes the name at a later step. WordPress then walks out of the theme folder and loads a different PHP file from the server (CWE-98, local file inclusion).
Think of a security guard who checks that a visitor's badge says "floor 3" and waves them in. The badge only decodes in the lift, and it actually says "boiler room".

Which sites are most at risk
Two conditions have to line up (WordPress security advisory):
- Your theme has a top-level folder whose name starts with
page-(for examplepage-templates). The advisory names the older default themes Twenty Twelve and Twenty Fourteen, plus Neve, Hestia and Sydney. If you use a child theme, check the parent too. - A PHP file useful to the attacker exists on the server. The known technique works when PHP's
register_argc_argvsetting is on. According to the advisory, it is on in the official PHP Docker image and in default cPanel setups running PHP older than 8.5.
With both in place, the result is remote code execution: someone else running commands on your server. With only the first, files on the server can be read.
Don't take comfort from your theme not being on that list. The list is examples, not a complete inventory, and the attacks don't check your theme first; automated tools simply try every WordPress site they find.
Is your site affected?
Three ways to check:
- In the dashboard: Dashboard → Updates. Your version is shown there, and if an update is waiting you can run it from the same screen.
- From the command line (if you have WP-CLI):
wp core version - From the outside, without logging in to anything: type your domain in the box below.
What is WP Lens? It's Noroxi's free WordPress scanner. You don't install anything or hand over a password: it reads the WordPress version, plugins and theme from what your site already shows publicly, then checks them against more than 30,000 known vulnerabilities across more than 14,000 plugins and themes. It also flags common misconfigurations, such as usernames that can be read from outside or open directory listings. If you hide your version, it will say so; use one of the first two options instead.
You don't have to wait for the next one. The speed of CVE-2026-87902 is no longer unusual: the gap between disclosure and the first attack is now measured in hours. Add your site to a free Noroxi account and WP Lens rescans it on a schedule. When a new vulnerability is published for a plugin, theme or WordPress version you run, you hear about it from us instead of finding it in the news. Create a free account, add your site once, and let the system keep watch. Rather not sign up? Every Monday we send one email with the vulnerabilities exploited that week.
Looking after more than one site, as an agency, a freelancer or an in-house IT team? Add them all to one list, watch them together and report to each site owner under your own name: Noroxi for multiple sites. For sites that hide their WordPress version, paste the plugin list into WP Lens and get results without a single request to the site.
What to do
1. Update today
WordPress backported the fix to every branch back to 4.7. If you can't move to the latest major version, moving to the patched release of your own branch is enough:
| Your branch | Patched release |
|---|---|
| 7.1 | 7.1.2 |
| 7.0 | 7.0.6 |
| 6.9 | 6.9.9 |
| 6.8 | 6.8.10 |
| 6.7 | 6.7.9 |
| 6.6 | 6.6.9 |
| 6.5 | 6.5.12 |
| 6.4 and older | See the full table at the end |
If automatic updates are on, you have most likely received it already, but check anyway: automatic updates can fail silently because of file permissions or a plugin.
2. If you can't update right away
If a custom theme or a hosting restriction stops you from updating today, Patchstack suggests two stopgaps:
- Block path traversal in the page name. In your firewall (WAF) or server rules, reject requests whose
pagenamevalue contains an encoded../. Real page names never contain it, so genuine visitors are unaffected. - Turn off
register_argc_argvin PHP. It doesn't close the hole, but it breaks the known route to code execution. In Patchstack's words, it is "the difference between an information leak and code execution". You can usually change it in your hosting panel's PHP settings or ask your host.
Both are temporary. The fix is the update.
3. After updating, look for traces
If you updated after 22 September, there is a good chance your site was probed in the meantime. Check:
- The
/tmpand/var/tmpfolders: attackers drop their files here. Unfamiliar.phpfiles there mean you should treat the server as compromised. - Access logs: requests whose
pagenamecontains an encoded../, and requests that sendpagenameandpage_idtogether to the site root or/index.php. - Successful (200) responses that return RSS or OPML content from an ordinary page URL: Patchstack gives this as a sign that an inclusion worked.
- Admin accounts and files: administrators added in recent weeks, modified core files (
wp core verify-checksums).
If you find anything: change the database password and the security keys in wp-config.php, rotate any third-party API keys stored there, and consider rebuilding the server from a clean backup.
Not sure?
If you can't tell whether your site was affected or attacked before you patched, or you need to check a number of sites together, get in touch with the Noroxi team. We'll look at it with you.
Record details
| Record | CVE-2026-87902 |
| Affected | WordPress core, 4.7.0 – 7.1.1 |
| Weakness | Path traversal leading to local file inclusion (CWE-98); remote code execution under conditions |
| Privileges needed | None: no account, no password, no user interaction |
| Severity | CVSS 4.0: 9.2 Critical (WordPress) · CVSS 3.1: 8.1 High (NVD) |
| Exploited in the wild | Added to CISA's Known Exploited Vulnerabilities catalog on 25 September 2026 |
| Exploit likelihood | EPSS 39%: higher than 98% of all records (18 October 2026) |
| National advisory | Türkiye Cybersecurity Directorate TR-26-1350, 16 October 2026 · all national advisories |
| Reported by | Robert Ressl |
Timeline
| Date | What happened |
|---|---|
| 22 September 2026 | WordPress 7.1.2 and the security advisory released. First attack attempt seen the same day at 11:49 UTC |
| 23 September | Ready-made scanning tools circulating; attack traffic ten times the first evening |
| 25 September | CISA adds the flaw to its exploited-in-the-wild catalog |
| 2 October | Exploit likelihood (EPSS) peaks at 45% |
| 16 October | Türkiye's Cybersecurity Directorate publishes an advisory |
Patched releases for every branch
| Branch | Patched | Branch | Patched |
|---|---|---|---|
| 7.1 | 7.1.2 | 5.8 | 5.8.17 |
| 7.0 | 7.0.6 | 5.7 | 5.7.19 |
| 6.9 | 6.9.9 | 5.6 | 5.6.21 |
| 6.8 | 6.8.10 | 5.5 | 5.5.22 |
| 6.7 | 6.7.9 | 5.4 | 5.4.23 |
| 6.6 | 6.6.9 | 5.3 | 5.3.25 |
| 6.5 | 6.5.12 | 5.2 | 5.2.28 |
| 6.4 | 6.4.12 | 5.1 | 5.1.26 |
| 6.3 | 6.3.12 | 5.0 | 5.0.29 |
| 6.2 | 6.2.13 | 4.9 | 4.9.33 |
| 6.1 | 6.1.14 | 4.8 | 4.8.32 |
| 6.0 | 6.0.16 | 4.7 | 4.7.37 |
| 5.9 | 5.9.18 |
Sources
- WordPress security advisory (GHSA-7hp8-65ch-5whp)
- Patchstack: Attackers started probing WordPress sites hours after the patch
- NVD: CVE-2026-87902
- CISA: Known Exploited Vulnerabilities Catalog
- Türkiye Cybersecurity Directorate: TR-26-1350
- Noroxi CVE record: day-by-day exploit likelihood and record changes
- Every recorded WordPress vulnerability
This post contains no exploit code and no links to attack tools.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.