WordPress security news, 9 November 2026: the update-window probes pass 240,000, and PHP2Shell now ends in root
A week after WordPress 7.1.4, Wordfence has blocked more than 240,000 requests for the staged installer that CVE-2026-119977 exposes during a Core update, with a peak of over 74,000 on 30 October, and has published the addresses that sent most of them. Patchstack’s exploited list now carries eleven plugin flaws that were not in last week’s briefing: three booking and affiliate plugins open to SQL injection or account takeover, a custom-fields add-on and a membership plugin that give code execution, Elementor, and a form plugin with no fix at all, which WPScan joins with a second. Wordfence’s weekly report counts 549 new vulnerabilities in 351 plugins and four themes. Below the application, the item that matters most was not in last week’s briefing: CISA listed the Fragnesia kernel flaw, CVE-2026-46300, on 28 October as being chained with PHP2Shell to plant webshells and run commands as root, and one research team has published a campaign that rooted 25 servers that way. nginx and Apache have both moved on as well, and the nginx bug circulating on social media this week dates from May.
Prepared by G. Schad, WordPress and Linux security specialist
CVE-2026-119977: over 240,000 blocked attempts per Wordfence, 74,000+ on 30 October alone; in CISA’s KEV from 3 November. Fixed in 7.1.4 and backports to 4.7.39; deny wp-content/upgrade/ at the web server
Plugins
Exploited per Patchstack: LatePoint 5.7.7, Amelia Pro 9.9.2, SliceWP 1.2.15, WP Data Access 5.5.90, ACF Extended PRO 0.9.2.7, Ultra Addons for CF7 3.5.55, s2Member 261001, BuddyBoss App 3.2.2, Elementor 4.3.6, Checkout Files Upload 2.4.0. No fix: WP Libre Form, CryptoPayment Gateway, WP Duplicate
Kernel and PHP
Fragnesia (CVE-2026-46300) in KEV since 28 October, chained with PHP2Shell to root; fixed upstream in May. CloudLinux ZDI-CAN-33367: every line now has a fixed kernel or a livepatch. PHP CVE-2026-115560 still unfixed
Web servers
nginx: run 1.30.6 stable or 1.31.8 mainline; CVE-2026-42945 is May’s bug, fixed in 1.30.1. Apache httpd 2.4.70 (6 November): bug and crash fixes, no new CVEs listed at the time; updated 16 November: 2.4.70 is affected by the critical CVE-2026-119618, run 2.4.71. Brotli CVE-2026-111497 KEV deadline 10 November
This week in one minute
The short version: what changed in the week to 9 November
If you read one section, read this one. The Core flaw is still the first item, not because anything new is broken but because the probing has not slowed: Wordfence counted more than 240,000 blocked attempts by 5 November, most of them from three addresses, and says the highest volume ran from 29 October to 1 November. Every one of those is a bet that a site is in the middle of a Core update at the moment the request lands. The fix is the same as last week, 7.1.4 or the branch backport plus a web-server rule that denies the upgrade folder, and the new work is reading your logs for the addresses and paths Wordfence has now published.
The plugin list is long, and the useful way to read it is by what an anonymous visitor gets. Code execution: ACF Extended PRO, s2Member and WP Libre Form. Someone else’s account: LatePoint and WP Data Access. The database: Amelia Pro and SliceWP. Files: Checkout Files Upload for WooCommerce, Ultra Addons for Contact Form 7, and BuddyBoss App for any subscriber. Elementor’s is a reflected cross-site scripting that needs a logged-in user to open a link, which on ten million installs is enough for Patchstack to see it used. Three have no fix and have to be removed. On the server, the news is a chain: PHP2Shell gives a shell as the web user, and Fragnesia, a kernel bug fixed upstream in May, turns it into root. Servers that took the PHP fix but not a kernel from the last six months are halfway protected.
Figure 1 · The week at a glance
The Core probing keeps climbing, eleven more plugins are exploited, and PHP2Shell now ends in root.
Component
Status on 9 November
What to do
WordPress Core ≤ 7.1.3 · CVE-2026-119977
240,000+ blocked probes; peak 74,000 on 30 Oct
7.1.4 or backport; deny wp-content/upgrade/; search logs
Update to the fixed versions; review admins and uploads
WP Libre Form · CryptoPayment Gateway · WP Duplicate
Exploited, no fix
Delete; rotate wallet keys
Linux kernel · Fragnesia CVE-2026-46300
KEV 28 Oct; chained with PHP2Shell to root
Kernel with the May fix, booted; PHP at 21 Oct release
CloudLinux · ZDI-CAN-33367
Fixed kernel or livepatch on every line
Reboot or apply KernelCare; confirm
nginx · Apache httpd
CVE-2026-42945 is May’s; 2.4.70 out 6 Nov
nginx 1.30.6 or 1.31.8; Apache 2.4.71 (see 16 Nov)
The six items that need action in the week to 9 November 2026: the Core update window, ten exploited plugins, three with no fix, the kernel half of the PHP2Shell chain, CloudLinux, and the web servers.
WordPress Core · the probing continues
Over 240,000 blocked requests for staged setup-config.php files under wp-content/upgrade/, peaking above 74,000 on 30 October. Wordfence names ten source addresses and says the update to 7.1.4 itself runs the vulnerable process one last time, which is why the deny rule goes in first. Free Wordfence installs get the firewall rule on 27 November.
Plugins · eleven exploited, three with no fix
Ten fixes to install, from LatePoint’s account takeover to s2Member’s code execution through PayPal IPN, plus Elementor 4.3.6. WP Libre Form was closed on WordPress.org on 8 September and has no patched version; CryptoPayment Gateway and WP Duplicate have none either. Remove all three.
Kernel · Fragnesia and the CloudLinux bug
CVE-2026-46300 is in CISA’s catalog with the note that it is chained with PHP2Shell to run commands as root. Kernels released before 13 May are affected. Separately, CloudLinux’s 5 November update says every affected line now has a fixed kernel or a livepatch for ZDI-CAN-33367, including 8 ELS and 9 ELS.
Web servers and PHP
nginx 1.30.6 stable and 1.31.8 mainline are current; the rewrite-module bug that went around on X this week was fixed in May and has been exploited since. Apache 2.4.70 shipped on 6 November with a mod_dav_lock heap overflow fix and the 2.4.69 regressions. PHP has nothing new: CVE-2026-115560 still waits for the next release.
Full write-ups
The week to 9 November, 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
The update-window RCE: 240,000 attempts, ten addresses and one last vulnerable update
What this week means: the chain from a request to root is no longer theoretical
For several weeks these briefings have described the same sequence on shared hosting: a vulnerable plugin or interpreter gives an attacker a shell as one account, and a local kernel bug turns that account into the server. This week a published campaign did it, with PHP2Shell for the first step and Fragnesia for the second, and CISA wrote the chain into its catalog. The defence is equally plain: every layer patched, because each one is a separate door. A server whose sites are all on current plugins but whose PHP is 8.4.26, or whose PHP is current but whose kernel predates May, is exposed at exactly one step.
The plugin list rewards the same kind of thinking. The flaws that matter most this week are in plugins that take public input by design, booking forms, affiliate sign-ups, checkout uploads, payment callbacks and membership IPN handlers, and in premium add-ons that update only with a licence. An inventory that records which plugins on each server accept anonymous input, and which ones depend on a licence to update, is what lets a fleet answer this week’s question in minutes rather than a day.
The Core probing is a reminder that maintenance is itself a window. Updates, migrations, restores and staging copies all create states that are not the normal running site, and attackers poll for them. A web-server rule that denies the folders WordPress uses for updates, uploads and caches to anything but the file system closes most of those states permanently, and it costs nothing to keep.
Today: Core and the logs, the exploited plugins, the three removals, kernel and PHP
In this order. Work from a trusted device, preserve logs before changing a server under suspicion, and record what you change.
01
Confirm Core and the deny rule everywhere
Every site on 7.1.4 or its branch’s backport, and wp-content/upgrade/ denied at the web server, added before any site still to be updated runs its update:
shell
$ wp core version --skip-plugins--skip-themes$ curl-s-o /dev/null -w"%{http_code}\n" https://example.com/wp-content/upgrade/index.php
The second command should print 403 for each site once the rule is in place. Then run the log searches in the Core section above.
02
Update the ten exploited plugins
Across every site on the server, list them with their versions:
shell
$ for s in /home/*/public_html;dowp plugin list --path="$s"--skip-plugins--skip-themes--fields=name,version--format=csv2>/dev/null|grep-E"^(latepoint|wp-data-access|ameliabooking|slicewp|acf-extended-pro|s2member|ultimate-addons-for-contact-form-7|checkout-files-upload-woocommerce|buddyboss-app|elementor),"|sed"s|^|$s |";done
Targets: LatePoint 5.7.8, WP Data Access 5.5.90, Amelia Pro 9.9.2, SliceWP 1.2.15, ACF Extended PRO 0.9.2.7, s2Member 261001, Ultra Addons for Contact Form 7 3.5.55, Checkout Files Upload 2.4.0, BuddyBoss App 3.2.2, Elementor 4.3.6, or the current release. A premium plugin that cannot update today gets deactivated.
03
Remove the three with no fix
WP Libre Form, CryptoPayment Gateway and WP Duplicate: copy any suspicious files for the case file, then delete the plugin folders. For CryptoPayment Gateway, move funds and rotate the wallet keys, and check the receiving address in the gateway settings.
Delete CryptoPayment Gateway by the folder name the inventory command in the no-fix section prints.
04
Review the exposure windows
For the plugins that give code or files, ACF Extended PRO, s2Member, Checkout Files Upload, BuddyBoss App and the three removals: PHP files in uploads and mu-plugins since 20 October, cron events, the account’s crontab and processes. For LatePoint and WP Data Access: administrators, role changes and sessions. For Amelia Pro and SliceWP: rotate what the database stored.
shell
$ find /home/*/public_html/wp-content/uploads /home/*/public_html/wp-content/mu-plugins -type f \( -iname"*.php*"-o-iname"*.phar"-o-iname"*.pht"-o-name".htaccess" \) -newermt"2026-10-20"-ls
05
Close both halves of the PHP2Shell chain
PHP at 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or a vendor build whose changelog lists both CVEs, on every branch a site uses; and a kernel that carries the CVE-2026-46300 fix, booted:
Where the kernel cannot be rebooted today, raise the server to the top of the window list: CISA’s deadline for agencies was 31 October.
06
Finish CloudLinux, Brotli and the web servers
CloudLinux: fixed kernel booted or the KernelCare patch applied for ZDI-CAN-33367, now available on every line except the 9 ELS livepatch. Brotli: the OS library by package revision and restarted processes, before the 10 November deadline. nginx to 1.30.6 or 1.31.8; Apache straight to 2.4.71 (corrected 16 November: 2.4.70 is affected by CVE-2026-119618).
The next 48 hours, and the hardening that keeps this week from repeating
24 to 48 hours · the inventory items
Easy Digital Downloads to 3.7.3, BuddyForms to 2.10.6, and Avada, The Grid and YOOtheme Pro to the vendor’s release after the vulnerable range. Check the six plugins from last week again, since they are still on the exploited list. Keep session.upload_progress.enabled at 0 until PHP fixes CVE-2026-115560.
24 to 48 hours · the server look-back
On any server that ran unpatched PHP after 17 October, look for the results of the chain: PHP files in web roots and temporary folders, setuid files and changed files under /etc that no package owns, root SSH keys and root cron entries. Copy logs off the server first.
This week · know which plugins take public input
Record, per server, which installed plugins expose endpoints to anonymous visitors: forms, bookings, checkouts, payment callbacks, registrations. Those are the ones to update the day a fix appears, and the ones to put behind a firewall rule when none has.
This week · licences and premium updates
List every premium plugin and theme, where its licence lives and whether it updates on its own. Amelia Pro, ACF Extended PRO, Avada, The Grid and YOOtheme Pro are all on this week’s list, and the premium plugins are the ones most often a version behind.
This week · deny the maintenance states
Keep wp-content/upgrade/ denied, forbid PHP execution in uploads and cache folders, forbid directory listing, and keep staging copies and migration plugins off public hostnames. Remove migration and backup plugins once the job is done.
This week · kernel and PHP on one schedule
Put kernel updates and reboots on the same calendar as PHP updates, with livepatching where it is available, so that the two halves of a chain like this week’s never drift six months apart.
Checklist
Thirty minutes per server: the ten checks that close this week
01
WordPress 7.1.4 or the branch backport on every site
From WP-CLI with plugins skipped, on every node, staging copy and replica.
02
wp-content/upgrade/ answers 403 from outside
Checked per site with a request, not assumed from the configuration file.
03
No successful request for PHP under the upgrade folder
Access logs searched for the paths and the ten published addresses, status codes noted.
WP Libre Form, CryptoPayment Gateway, WP Duplicate, deleted rather than deactivated, with wallet keys rotated where CryptoPayment was used.
06
PHP at the 21 October releases or a vendor backport
On every branch any site uses, from the interpreter and the package changelog.
07
The running kernel carries the CVE-2026-46300 fix
uname -r compared against the distribution’s advisory, after a reboot if a new kernel was installed.
08
CloudLinux ZDI-CAN-33367 closed
Fixed kernel booted or KernelCare patch applied; user.max_user_namespaces at 0 where neither is possible yet.
09
Brotli, nginx and Apache current
brotli-libs or libbrotli1 by revision with old copies out of memory; nginx 1.30.6 or 1.31.8; Apache 2.4.71 or a backport (corrected 16 November: 2.4.70 is affected by CVE-2026-119618).
10
Logs preserved and a ticket opened for every match
Anything above that matched gets a case, with the logs copied off the server before cleanup starts.
Sources
Where every claim in this briefing comes from
This briefing was compiled on 9 November 2026. Versions, dates and figures are quoted as the source reported them and were not independently re-measured. The Core attack figures, addresses and firewall timing are from Wordfence’s 5 November post, read through its feed; the catalog dates for CVE-2026-119977, CVE-2026-46300, Brotli and PHP2Shell are from CISA’s catalog data, which gives 3 November for the Core flaw where Wordfence writes 2 November. Exploitation status for plugins is Patchstack’s known-to-be-exploited label as shown on its database on 9 November, and fixed versions are Patchstack’s, checked against the WordPress.org listings and changelogs for the plugins hosted there; Amelia Pro and ACF Extended PRO are premium, so their fixed versions are Patchstack’s alone. WP Duplicate’s status is WPScan’s; CryptoPayment Gateway’s is the CVE record’s, with the exploitation report attributed to Defused in secondary coverage. The weekly counts and the EDD, Avada, The Grid and YOOtheme Pro entries are from Wordfence’s weekly report; BuddyForms and EDD descriptions are from their CVE records. The Fragnesia campaign figures are Dream Security’s as reported by BleepingComputer and were not read at the source; the kernel description is the CVE record’s and the Debian versions are from Debian’s tracker. CloudLinux’s status is from its advisory as updated on 5 November. nginx and Apache details are from nginx.org and the Apache project’s own pages; the CVE-2026-42945 trigger conditions and exploitation date are from secondary reports of VulnCheck’s findings. The research notes this issue started from attributed the PHP2Shell honeypot finding to Kaspersky, gave ACF Extended PRO’s fix as 0.9.2.8 and nginx’s as 1.30.1, and described Brotli exploitation as contested; each was checked and corrected as described in the text. Updated on 16 November 2026: the advice to run Apache httpd 2.4.70 now points to 2.4.71, because 2.4.70 is affected by CVE-2026-119618; nothing else in this briefing was re-checked.
The week to 9 November left something to check: choose the response path.
The server under the sites
Get both halves of the PHP2Shell chain checked and proven on every host.
Best when several servers need PHP and the kernel verified from the running process rather than the repository, the Core update window and the published addresses searched in the logs, and the post-exploitation look-back done once, with a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when an exploited booking, membership or form plugin left an administrator or a PHP file behind, a plugin with no fix was installed, or a cleaned site has come back, and you want every layer removed in one pass rather than one at a time.