WordPress security news, 5 October 2026: from patching to incident response
The work this week moves from updating WordPress to finding out what got in before the update. The Core file-inclusion flaw fixed in 7.1.2 on 22 September has gone from probing to real attempts at remote code execution, cPanel fixed a flaw on every supported branch that ends in commands running as root, and six plugins shipped critical or high-severity fixes. This briefing covers what changed in the week to 5 October, the indicators to search for, and the actions in priority order.
Prepared by G. Schad, WordPress and Linux security specialist
7.1.2, released 22 September — no newer release as of 5 October 2026; 7.2 is due 8–10 December
This week in one minute
The short version: what changed in the week to 5 October
If you read one section, read this one. Last week the urgent job was getting every site onto WordPress 7.1.2. This week the urgent job is checking whether anything got in before that update landed — because the flaw it fixes is now being used to run code on servers, not just to probe them.
The hosting layer had a busy week too. A login on a cPanel server can now be the starting point of an attack on the server itself: through the Multilang Adminbin flaw fixed on 29 September, which needs only a low-privileged account, or, on CloudLinux 7h and 8, through a kernel bug that an ordinary hosting account can reach as shipped. On a shared server, that turns one hacked WordPress site into everybody’s problem.
Figure 1 · The week at a glance
One Core flaw exploited, six plugins to update, two paths from a server login to root.
Component
Status on 5 October
What to do
WordPress Core ≤ 7.1.1
Exploited: pearcmd.php RCE, on CISA KEV
Update to 7.1.2; search logs from 22 Sep
Request a Quote for WooCommerce ≤ 2.9.2
Unauthenticated file upload, CVSS 9.8–10
Update to 2.9.3; check uploads for PHP
Elementor 4.3.0–4.3.1
Every REST route open to CSRF
Update to 4.3.2
cPanel & WHM, every branch
Low-privilege login to root, CVSS 9.9
Fixed build for the branch
CloudLinux 7h, 8, 8 LTS
Local user to root (CVE-2026-72389)
Fixed kernel or KernelCare
The five items that need action in the week to 5 October 2026: a Core flaw exploited in the wild, the two most urgent plugin updates, and two flaws that let a low-privileged login on a server reach root.
WordPress Core · CVE-2026-87902
The unauthenticated file-inclusion flaw fixed in 7.1.2 is now being chained to pearcmd.php to write and run PHP wherever the conditions allow. CISA added it to its Known Exploited Vulnerabilities catalog on 25 September.
Plugins · six to update
Request a Quote for WooCommerce 2.9.2 and earlier lets anyone upload a file without logging in. The vendor fixed it in 2.9.3 on 26 September, although Patchstack’s database still listed no fix on 5 October. Five other plugins have critical or high-severity fixes.
cPanel and WHM · root
Three critical fixes shipped on 29 September for every supported branch. The worst, CVE-2026-93698 (CVSS 9.9), lets a low-privileged login run commands as root through the Multilang Adminbin.
WordPress Core release
No new version this week. 7.1.2 is still the latest release and the only maintained 7.1 version. No 7.1.3 has been announced; 7.2 is scheduled for 8–10 December.
Full write-ups
The week to 5 October, item by item: where each is covered in full
The mechanism, affected versions, indicators and commands for each item are on the page named beside it. Those pages are updated as each story moves; this briefing stays as the record of the week.
This week’s item
Covered in full on
CVE-2026-87902: from probing to real code-execution attempts
Self-healing malware, 319 plugin flaws in one week, and the quarter in numbers
Sucuri · “SC” self-healing malware
Sucuri described a WordPress infection that “lives in at least eight places at once, spread across files, the database, and shared memory”, where each copy can rebuild the others. The practical lesson: removing copies one at a time loses the race, so every layer has to go in the same pass. Published 30 September. Imunify360 uses the same name for a campaign it found on more than 120,000 sites across 9,000 servers in the two weeks to 17 September.
Wordfence · plugin flaws, 21–27 September
319 vulnerabilities disclosed in 222 plugins in a single week, 14 of them critical and 13 still unpatched when the report went out on 1 October. Request a Quote for WooCommerce is among the 9.8-rated entries, alongside Meta Box AIO up to 3.11.0 and miniOrange OTP up to 5.5.5.
Wordfence · Q2 2026 threat report
2,073 vulnerabilities disclosed in the quarter, 10.4 billion attacks blocked by its firewall, and 573,000 infected sites detected. Published 29 September.
What this week means for cleanups and for shared servers
For any cleanup after CVE-2026-87902, “the site is updated and the scanner is clean” is no longer enough to call it finished. The payload in the observed attacks is written outside the web root, to /tmp and /var/tmp, where WordPress security plugins do not look. If you find any trace of pearcmd or PHP in a temporary directory, treat the server as compromised: review running processes, cron jobs for every account, SSH authorized_keys, neighbouring accounts, and persistence outside public_html.
On cPanel servers, a single compromised hosting account can now be the starting point for attacks on the WHM administrator’s session, through the two stored cross-site scripting flaws, or on the host itself, through the CloudLinux kernel bug and potentially the Multilang Adminbin flaw, whose advisory does not say which accounts can reach it. Until both are patched, the boundary of an incident on a shared server is the server, not the site.
Malicious service workers remain another explanation for reinfections that leave no visible change on the server. The worker is registered in the browser’s own storage, so cleaning the server does nothing to it: the next time a browser with a WordPress login cookie opens the site, the worker runs first and puts the malware back. Imunify360 announced on 22 September that version 4.1.2 of its WordPress plugin lists the service workers registered for a site during signed-in sessions, unregisters the malicious ones, and purges their caches. It is rolling out over the coming weeks, and the host has to switch it on with a server-wide setting; a site owner cannot enable it alone.
The first two are read-only checks. Run them from a trusted device, and if anything produces a result you cannot explain, preserve it before changing anything.
01
Verify every Core version today
Every site should be on 7.1.2 or the security release for its branch. Then review the access logs from 22 September onward, even for sites that are already patched.
02
Search for the CVE-2026-87902 indicators
Look for pearcmd, config-create, and encoded traversal in pagename in the logs, and for recently modified PHP in /tmp, /var/tmp, wp-content/uploads, cache directories, and mu-plugins. Check whether the active theme has a page- directory and whether pearcmd.php is reachable with register_argc_argv on; if both are true, assume the worst until the checks say otherwise.
03
Update Request a Quote for WooCommerce to 2.9.3
The update comes through WooCommerce.com, not the plugin directory. If a site cannot be updated today, deactivate the plugin until it can, and check the quote upload folders and wp-content/uploads for PHP files either way.
04
Update the other five plugins, then audit access
Apply the fixed versions in the table above, then review administrators, sessions, application passwords, and recent changes in wp_options on every site that ran a vulnerable version.
05
Check the cPanel build
Run /usr/local/cpanel/cpanel -V and compare it with the fixed version for its branch; run /usr/local/cpanel/scripts/upcp --force if it is behind.
06
Apply EasyApache 4 v25.86
Then confirm that every PHP version the accounts actually use was updated, not just the default.
07
Patch CloudLinux kernels
Check the running kernel and the livepatch coverage:
If you use the interim mitigation, write it as install bridge /bin/false, and never on hosts with Docker, LXC, libvirt, or bridged networking.
08
Look for AI-tool credential files in web roots
Search document roots, web-accessible backups, and published home directories for .codex, .claude, .config/claude, and .anthropic credential files and their backup copies. If one was reachable over HTTP, rotate the token.
09
Confirm the WAF is on and updating
Check that ModSecurity or the Imunify360 WAF is active and that automatic rule updates are running.
This briefing was compiled on 5 October 2026 from the published sources below. Versions, dates, and figures are quoted as the source reported them and were not independently re-measured. Where a claim rests on a single source, the source is named next to it in the text.
The week to 5 October left something to check: choose the response path.
One site, one worrying result
Get the finding classified and the site restored to a trusted state.
Best when a log search turned up pearcmd requests, PHP in a temporary directory, or an administrator nobody created, and you want it handled properly rather than deleted and hoped for.