Tracker · Exploited plugins · November 2026

Exploited WordPress plugins, November 2026: flaws and fixed versions

The plugin sections of the November 2026 weekly briefings in one place. Six flaws were reported as exploited in the week to 2 November and ten more in the week to 9 November. In the week to 16 November, the AutomatorWP Pro Webhooks add-on joined them, along with wpForo and Bricksforge, and three add-ons disclosed file upload, write or deletion flaws rated 10 that need no login. Three exploited plugins have no patched version and have to be removed. Each table names the fixed version, and each section says where the exploited label comes from.

This page collects the plugin sections of the weekly briefings of 2, 9 and 16 November 2026, oldest first. Each section is dated; a plugin listed in an earlier week stays on the list until its fix is installed.

Week to 2 November
Six exploited: Contact Form 7, Gravity Forms, WP Project Manager, FunnelKit Automations, Uncanny Toolkit for LearnDash, WP Social
Week to 9 November
Ten more, including LatePoint, Amelia Pro, ACF Extended PRO, s2Member and Elementor
Week to 16 November
Exploited: AutomatorWP Pro Webhooks, wpForo, Bricksforge; three CVSS 10 file flaws with no login needed
No fix
WP Libre Form, CryptoPayment Gateway and WP Duplicate: remove them
After updating
Review administrators and uploads; an update does not remove what an exploit already left

2 November · Plugins · exploited

Six plugin flaws under exploitation, from a 10-million-install form to a 5,000-install project board

Patchstack marks all six as known to be exploited. The fixed version is the one to install; the current version on WordPress.org is given where it has moved on. Three are usable by anyone against a stock install; the other three need something from the server or the site.

Contact Form 7 is the one most people will find on their servers, and the one whose severity most depends on the server. The vendor’s 29 October notice says the target is any form with a file field on a server that lists directory contents; Patchstack adds that the upload folder name is random and not disclosed, so an attacker who cannot list the directory has to guess. Two server settings decide the outcome: whether Options -Indexes, or the nginx equivalent, is in force for the uploads tree, and whether PHP executes there at all. A site that already forbids PHP in wp-content/uploads and does not list directories has turned this from a takeover into a storage nuisance. Update to 6.2.4 anyway, then look in the wpcf7_uploads folder and the rest of uploads for anything with a PHP, phar, pht or phps extension, a double extension, or a .htaccess that was not there before.

The three that need nothing from the server are the ones to treat as incidents on any site that was exposed. WP Project Manager’s flaw is plain remote code execution reachable from the internet, and its 4.1.2 changelog describes it only as a fix to how project changes are checked before saving. Uncanny Toolkit and WP Social both let a visitor become an existing user, which on a LearnDash or membership site means the administrator who set it up. For those three, review administrators, role changes, password resets and sessions since the fix dates, and look for PHP in uploads, mu-plugins and cron on the Project Manager sites. Gravity Forms and FunnelKit are object injections: no gadget chain, no code execution, but Patchstack marks both exploited, which means someone is sending the payloads and finding chains somewhere. Gravity Forms is a premium plugin that does not auto-update by default and whose fix shipped on 1 October under a one-line changelog, so a site that watches only for security releases has been exposed for a month.

Figure 1 · At a glance

Three weeks of exploited plugin flaws, three plugins with no fix, and CVSS 10s with no login.

QuestionAnswer
Week to 2 NovemberSix exploited: Contact Form 7, Gravity Forms, WP Project Manager, FunnelKit Automations, Uncanny Toolkit, WP Social
Week to 9 NovemberTen more: LatePoint, Amelia Pro, SliceWP, WP Data Access, ACF Extended PRO, s2Member, Elementor and others
Week to 16 NovemberExploited: AutomatorWP Pro Webhooks, wpForo, Bricksforge; three CVSS 10 file flaws
No fixWP Libre Form, CryptoPayment Gateway, WP Duplicate: remove
After updatingReview administrators and uploads on every site that ran a listed version
The points that decide what to do about the WordPress plugins reported as exploited in the November 2026 briefings, as stated in the sections below.
Plugin and CVEVulnerableFixWhat an attacker gets
Contact Form 7 — no CVE yet, CVSS 8.16.2 to 6.2.36.2.4 (current: 6.2.4.1)Unauthenticated file upload through the feedback REST route. 6.2 removed the file-type check that ran before storage, so files land in the wpcf7_uploads folder before validation and rejected files stay; the remaining blocklist misses phar, pht, phps and .htaccess. The folder name is random, which is why Patchstack rates complexity high and priority medium. 10 million installs
Gravity Forms — CVE-2026-103039, CVSS 9.8≤ 3.1.23.1.3 (current: 3.2.1)Unauthenticated PHP object injection through a List-type Post Custom Field; code execution if the site carries a gadget chain. A proof of concept is public. Fixed on 1 October with a changelog line reading only “security enhancements”, four weeks before disclosure
WP Project Manager — CVE-2026-116512, CVSS 9.8≤ 4.1.14.1.2Unauthenticated remote code execution: a REST route’s validation callback runs before its permission check, so the plugin’s capability gate is never reached. A public exploit exists. 5,000 installs
FunnelKit Automations — CVE-2026-39738, CVSS 9.8≤ 3.8.6.13.8.6.2 (current: 3.9.0)Unauthenticated PHP object injection; code execution depends on a gadget chain. The 3.8.6.2 changelog says “hardened data validation across abandoned cart capture and contact fields” and never uses the word security. 20,000 installs
Uncanny Toolkit for LearnDash — CVE-2026-119096, CVSS 9.8≤ 3.8.23.8.3Unauthenticated authentication bypass through the email parameter of the front-end login action: log in as an existing user without the password. The changelog also records a two-factor integration that completed a login without applying the second factor. 20,000 installs
WP Social (Wp Social Login and Register Social Counter) — CVE-2026-103898, CVSS 8.1≤ 3.2.23.2.3Unauthenticated authentication bypass: the social-login REST callback’s permission check always passes and the account is matched by the email string the OAuth provider returns. Fixed on 14 October, published as exploited on 30 October. 70,000 installs

2 November · Plugins and themes · not yet exploited

Three more to inventory this week: FormFlow, Web 2.0 Directory and the Newsmatic theme

No exploited label on any of these as of 2 November. Two are SQL injections and one is an unauthenticated upload, which is the kind that gets a label within days.

Web 2.0 Directory is the awkward one: it is not on WordPress.org, its CVE record names no fixed version, and the secondary reports disagree between 2.10.13 and 3.0.0. Check the vendor’s changelog on CodeCanyon for the entry that mentions the level filter, and treat anything at 2.10.12 or below as vulnerable until then. FormFlow is the one to move first, because an unauthenticated upload with a public nonce is the pattern that goes from published to exploited fastest.

Component and CVEVulnerableFixWhat an attacker gets
FormFlow, listed on WordPress.org as SimpleForm — CVE-2026-118235, CVSS 9.8≤ 3.10.23.11.0Unauthenticated file upload: a trailing dot on the file name bypasses the extension and MIME checks in the upload handler, and the only token needed is a nonce printed into every public form
Web 2.0 Directory, sold on CodeCanyon — CVE-2026-15272, CVSS 6.5≤ 2.10.12Later than 2.10.12; the vendor changelog gives 3.0.0Time-based SQL injection through the level filter parameter, which is used unquoted in an integer context so WordPress’s slash escaping does nothing. The CVE record calls it unauthenticated and scores it with low privileges required; read the record before deciding which
Newsmatic theme — CVE-2026-110184, CVSS 7.5 (Patchstack: 9.3)≤ 1.5.01.5.1Unauthenticated blind SQL injection through the slug parameter in the theme’s functions.php. 1.5.1 removes the parameter from the query

9 November · Plugins · exploited

Ten exploited plugin flaws not covered last week, and the version that closes each

Every row carries Patchstack’s known-to-be-exploited label as of 9 November. The fix is Patchstack’s patched version; where WordPress.org has a later release, it is given as current. The six from last week, Contact Form 7, Gravity Forms, WP Project Manager, FunnelKit Automations, Uncanny Toolkit and WP Social, are still on the list.

The booking and affiliate plugins are the pattern of the week. LatePoint, Amelia and SliceWP all expose endpoints that the public is meant to reach, because customers book appointments and affiliates register without an account, and all three trusted what came in. A SQL injection on a booking site reads the customer table and the password hashes; an authentication bypass skips that step. For LatePoint and WP Data Access, review administrators, role changes and sessions since late October; for Amelia Pro and SliceWP, treat the database contents as read and rotate what is stored there, including API keys for payment and calendar integrations.

ACF Extended PRO, s2Member and Checkout Files Upload give code or files on disk, so a site that ran the vulnerable version since late October gets the full look: PHP files in uploads and mu-plugins by date, cron events, the account’s crontab and its processes. Ultra Addons for Contact Form 7 deletes files rather than writing them; check that wp-config.php and .htaccess are intact and that the site was not sent back to the installer. Two of the premium plugins, Amelia Pro and ACF Extended PRO, update only with a valid licence and are the ones most likely to be a version behind.

Plugin and CVEVulnerableFixWhat an anonymous attacker gets
LatePoint — CVE-2026-118066, CVSS 9.8≤ 5.7.65.7.7 (current: 5.7.8)Authentication bypass: log in as another user without the password. 100,000 installs. 5.7.8 adds a second security fix credited to Wordfence, so go to 5.7.8
WP Data Access — CVE-2026-118267, CVSS 9.8 (Patchstack)≤ 5.5.895.5.90 (current: 5.5.92)Privilege escalation: the app write endpoints pass attacker-supplied keys and values to insert, update and delete without the row filter. The CVE record scores it 8.1. 10,000 installs
Amelia Pro — CVE-2026-116751, CVSS 9.34.0 to 9.9.19.9.2Unauthenticated SQL injection. The free Amelia on WordPress.org is a separate 2.x line; this is the premium plugin, which updates through its licence
SliceWP — CVE-2026-120043, CVSS 9.3≤ 1.2.141.2.15Unauthenticated SQL injection in the affiliate plugin; the 1.2.15 changelog says only “variable escaping”. 10,000 installs
ACF Extended PRO — CVE-2026-120534, CVSS 10≤ 0.9.2.60.9.2.7Unauthenticated remote code execution. Premium; the free ACF Extended is not this entry
s2Member — CVE-2026-86596, CVSS 10≤ 260927261001 (current: 261106)Unauthenticated remote code execution, reported to run through the PayPal IPN handler, with a public proof of concept reported on 2 November. 8,000 installs
Ultra Addons for Contact Form 7 — CVE-2026-102435, CVSS 8.6≤ 3.5.543.5.55 (current: 3.5.57)Unauthenticated PHP object injection leading to arbitrary file deletion; deleting wp-config.php is the classic route to a reinstall and takeover. 60,000 installs
Checkout Files Upload for WooCommerce — CVE-2026-103688, CVSS 10< 2.4.02.4.0 (current: 2.4.1)Unauthenticated arbitrary file upload. 2.4.0 stops a blank accepted-types setting from meaning “any file”, so check the setting after updating
BuddyBoss App — CVE-2026-76124, CVSS 8.8≤ 3.2.13.2.2Arbitrary file upload for any Subscriber, so on a community site with open registration, effectively anyone
Elementor — CVE-2026-109884, CVSS 7.1≤ 4.3.54.3.6Reflected cross-site scripting: a logged-in user has to open a crafted link, and an administrator who does hands over the session. 10 million installs; 4.3.6 shipped on 2 November

9 November · Plugins · no fix

Three exploited plugins with no patched version: remove them

No update will arrive in time for any of these. A web application firewall rule buys hours; removing the plugin is the fix. Deactivating is not enough for a file-upload or AJAX flaw if the plugin’s files can still be requested directly, so delete the folder.

For CryptoPayment Gateway, removal is not the end: the wallet credentials the plugin stored should be treated as read, so move funds and rotate the keys from a clean device, and check the gateway settings in WooCommerce for a changed receiving address before taking another payment. For WP Libre Form and WP Duplicate, look for PHP in uploads and in the plugin’s own folder before deleting it, and keep a copy of what you find for the case file.

Find all three by name as well as by folder, because a migration plugin is often renamed or left in a staging copy:

shell
for s in /home/*/public_html; do wp plugin list --path="$s" --skip-plugins --skip-themes --fields=name,title,status,version --format=csv 2>/dev/null | grep -iE "wp-libre-form|local-sync|wp duplicate|cryptopayment" | sed "s|^|$s |"; done
Plugin and CVEVulnerableStatusWhat an attacker gets
WP Libre Form — CVE-2026-118423, CVSS 10≤ 1.5.0.1No patched version; closed on WordPress.org on 8 September for a security issueUnauthenticated file upload to code execution. Exploited per Patchstack
CryptoPayment Gateway — CVE-2026-81648, CVSS 101.2.1 to 1.2.2No fix listed in the CVE recordAn unguarded AJAX endpoint runs administrative operations for anyone: delete files on the server, overwrite the gateway settings, and read the stored wallet credentials in clear text. Exploitation attempts reported by Defused; not in CISA’s catalog
WP Duplicate (slug local-sync) — CVE-2026-123751≤ 1.1.11No known fix per WPScanAn authentication value that is not properly checked and an upload with no path or type validation: arbitrary file write and code execution. WPScan marks it actively exploited. About 200 installs, so this matters to agencies that used it for migrations and left it behind

9 November · Plugins and themes · not yet exploited

Five more to update before they get the label: EDD, BuddyForms, Avada, The Grid, YOOtheme Pro

No exploited label on these as of 9 November. Each needs no login, and two are commercial themes or builders that are installed far more widely than their vendors’ public numbers suggest.

Component and CVEVulnerableFixWhat an attacker gets
Easy Digital Downloads — CVE-2026-120538, CVSS 8.1≤ 3.7.23.7.3Administrator takeover through PayPal guest checkout: the guest email is trusted as proof of identity and the order, then the account, is bound to the existing user with that address. 40,000 installs
BuddyForms — CVE-2026-107622, CVSS 9.8≤ 2.10.52.10.6Privilege escalation through form-type confusion: a public form can be made to create a WordPress-internal object, including a registration with a site-managing role. 2.10.6 blocks both
Avada — CVE-2026-115346, CVSS 8.1≤ 7.16.2Later than 7.16.2; check the vendor’s changelogUnauthenticated arbitrary file upload through the Avada form upload field, per Wordfence’s weekly report
The Grid≤ 2.8.1Later than 2.8.1Unauthenticated remote code execution; Wordfence shipped a firewall rule last week
YOOtheme Pro5.0.0 to 5.0.52Later than 5.0.52Unauthenticated arbitrary file upload; Wordfence shipped a firewall rule last week

9 November · The week in numbers

549 vulnerabilities in a week, and how to read a list that long

Wordfence’s report for 26 October to 1 November counts 549 vulnerabilities in 351 plugins and four themes: 508 patched and 41 not, with 17 rated critical, 132 high, 394 medium and six low. Cross-site scripting leads with 209, missing authorisation follows with 128, and deserialisation with 35 is third, which is the class behind last week’s Gravity Forms and FunnelKit entries. 222 researchers contributed. Nobody patches 549 things in a week, and nobody needs to.

Three questions sort the list. Does it need a login, and if so, can anyone get one on your sites? Is it marked exploited, by Patchstack, WPScan, Wordfence or CISA? And is the plugin installed somewhere you are responsible for? An unauthenticated flaw with an exploited label in a plugin you run is today; an unauthenticated flaw without the label is this week; anything needing Contributor or higher on a site with three trusted editors is the next maintenance window. The 41 unpatched entries are the ones to read in full, because for them the only actions are a firewall rule or removal.

16 November · Plugins · exploited

Exploited: AutomatorWP Pro Webhooks and wpForo, plus WP Duplicate and Bricksforge

Each row says where its exploited label comes from. Patchstack’s known-to-be-exploited marker was read on each database entry on 16 November; WP Duplicate’s label is WPScan’s.

AutomatorWP is the one to act on first, and the one most likely to be misjudged. The flaw is in the paid Webhooks add-on, not in AutomatorWP itself, and only an automation that receives a webhook and identifies the user by ID is exploitable. That narrows who is affected. It doesn’t make the rest safe to postpone, because a webhook configuration is easy to forget and the fix is a point release. Update, then review password resets and administrator logins since early November on every site where the add-on was active.

wpForo’s two SQL injections were published on 6 November, and Patchstack has seen both exploited. The plugin has shipped three releases since, 3.2.3 to 3.2.5, and each one lists security fixes in its changelog. Forums are public by design, so anyone can reach the vulnerable endpoints. Go to 3.2.5 rather than the first fixed version. On a forum that ran 3.2.2 or earlier, treat the user table as read and force password resets for moderators and administrators.

Plugin and CVEVulnerableFixWhat an anonymous attacker gets, and the label
AutomatorWP Pro Webhooks add-on — CVE-2026-126173, CVSS 9.8≤ 1.4.41.4.5An arbitrary password reset, and with it account takeover, through a webhook trigger that identifies the user by ID. Patchstack marks it known to be exploited; published 13 November
wpForo Forum — CVE-2026-95870 and CVE-2026-119155, CVSS 9.3 each≤ 3.2.1 · ≤ 3.2.23.2.2 · 3.2.3 (current: 3.2.5)Two unauthenticated SQL injections: read access to the database, password hashes included. Patchstack marks both known to be exploited; published 6 November. The same versions also let a Subscriber escalate their wpForo group and delete files
WP Duplicate (slug local-sync) — CVE-2026-123751≤ 1.1.11NoneUnauthenticated file upload to code execution. Unchanged since last week: WPScan says it is actively exploited and has no known fix, and updated the entry on 15 November. Remove it
Bricksforge — CVE-2026-85097, CVSS 10≤ 3.1.8.93.1.8.10Unauthenticated file upload through the temporaryFileUploads parameter. Published by Patchstack on 7 October and marked known to be exploited; not covered here before. A premium add-on for the Bricks builder

16 November · Plugins · unauthenticated file upload, write and deletion

Three CVSS 10 file flaws: Ultimate Addons for Elementor Forms, Cloud Storage Manager, File Upload to Order

None of these carried an exploited marker on 16 November; “expected to become exploited” on their entries is Patchstack’s standard wording for high-priority flaws, not a report of attacks. All three need no login, Patchstack rates all three 10, and each one ends in control of the site. That is why they come ahead of this week’s cross-site scripting fixes even without the label.

Deletion belongs on the same list as upload. Deleting wp-config.php sends WordPress back to its installer, and an attacker who reaches the installer first can connect the site to a database they control, create an administrator and upload PHP. Deleting .htaccess removes whatever protection lived there, such as a rule that stops PHP running in uploads. Everest Forms (≤ 3.6.2, fixed in 3.6.3) and Drag and Drop File Upload for Elementor Forms (≤ 1.6.2) also disclosed unauthenticated file deletion this week; both are in the table further down.

After updating, look for what an upload or a write would have left, by date, and check that the files a deletion would target are still there:

shell
find /home/*/public_html/wp-content/uploads -type f \( -iname "*.php*" -o -iname "*.phar" -o -iname "*.pht" \) -newermt "2026-10-15" -ls
for s in /home/*/public_html; do [ -f "$s/wp-config.php" ] || [ -f "$s/../wp-config.php" ] || echo "no wp-config.php: $s"; done
Plugin and CVEVulnerableFixWhat an anonymous attacker gets
Ultimate Addons for Elementor Forms — CVE-2026-124814< 1.0.81.0.8Unauthenticated arbitrary file upload: a PHP file in the web root, then code execution
Cloud Storage Manager for Fluent Forms — CVE-2026-120522≤ 1.2.01.2.5Unauthenticated arbitrary file write; published 14 November
File Upload to Order — CVE-2026-107594< 1.1.41.1.4Unauthenticated arbitrary file deletion, using a file path taken from session data the attacker controls. Patchstack files it under its file-upload class, but its entry title and the CVE record both describe a deletion

16 November · Plugins · public proof of concept

ELEX HelpDesk: unauthenticated object injection with a public exploit, and a nonce that protects nothing

ELEX WordPress HelpDesk & Customer Ticketing System 3.3.9 and earlier has an unauthenticated PHP object injection that Patchstack scores 9.8. Patchstack lists it as CVE-2026-125855 and notes a possible collision with CVE-2026-119077, the identifier other trackers use. A proof of concept was reported on GitHub on 14 November. ELEX released 3.4.0 on 12 November. Its changelog says only “Security fix: Resolved a vulnerability issue”, and Patchstack lists it as the fixed version. No exploitation has been reported. The plugin has about 200 active installations, and this is its third unauthenticated flaw in a month: a file upload in 3.3.7 and earlier, published on 15 October, and a file deletion in 3.3.8 and earlier, published on 6 November.

The write-ups describe the mechanism like this. The plugin unserialises a ticket field without restricting which classes may be created, and the only check in front of it is a WordPress nonce. That nonce is printed on any page that carries the support shortcode, so anyone can read it from the public page and send it back. A nonce stops a logged-in user from being tricked into an action. It says nothing about who is sending the request, and on an endpoint open to visitors it is not authentication. The same pattern is behind a good share of “unauthenticated” plugin flaws.

Update to 3.4.0. On a site where the help desk is not essential, three unauthenticated flaws in four weeks is a reason to consider removing it. Access logs do not record request bodies, so the most they can show is a burst of POST requests to admin-ajax.php from an address that has just loaded the support page. A web application firewall’s logs are better evidence.

16 November · Plugins · also disclosed this week

Six more to update, and how to read “only if this setting is on”

None of these carried an exploited label on 16 November. The fixed versions are the ones the database entries state, where they state one.

Third-party roundups this week also list Widget Options (≤ 4.2.6.1, PHP code injection for Authors and above, CVE-2026-116615), SureDash (≤ 1.13.0, Portal Manager to administrator, CVE-2026-123769), NextGEN Gallery (≤ 4.5.5, file deletion for users who can manage galleries, CVE-2026-118191), Gutenverse Form (< 3.2.2, CSV formula injection, CVE-2026-124018) and ElasticPress (≤ 5.3.5, unauthenticated stored cross-site scripting, fixed in 5.3.6). We did not check those entries at the source. Each needs a trusted role or has a narrower effect, so update them in the normal cycle.

This week’s exploited entry is also the clearest example of a conditional critical. AutomatorWP Pro Webhooks scores 9.8, but it can only be exploited through a webhook that identifies the user by ID. Read the condition, then check it on your own sites; don’t assume either way. A condition that is true on one site in fifty leaves a fifty-site fleet exposed. A condition that cannot be true on your setup moves the update to the next window, and no further.

Plugin and CVEVulnerableFixWhat an attacker gets
Shipo — CVE-2026-19907, CVSS 9.81.6 to 1.8.01.8.1Authentication bypass to administrator with no login; published 14 November
Advanced Form Integration — CVE-2026-125769, CVSS 9.8≤ 2.11.32.11.5Privilege escalation; Patchstack nonetheless rates its priority low. The plugin’s third critical-scored flaw since October, after an unauthenticated password change in 2.9.0 and earlier and an unauthenticated object injection in 2.10.2 and earlier
User Verification (PickPlugins) — CVE-2026-76792, CVSS 8.1< 2.0.492.0.49Unauthenticated account takeover
Everest Forms — CVE-2026-120513, CVSS 8.6≤ 3.6.23.6.3Unauthenticated arbitrary file deletion. A separate unauthenticated file read, which can expose wp-config.php, affects 3.6.3 and earlier, so update to the current release
Drag and Drop File Upload for Elementor Forms≤ 1.6.2Later than 1.6.2Unauthenticated arbitrary file deletion
Ultra Addons for Contact Form 7 — file read≤ 3.5.543.5.55 or laterUnauthenticated arbitrary file read through the PDF Generator add-on. Same range as last week’s exploited object injection, so a site already on 3.5.55 or later is past both

16 November · The week in numbers

497 vulnerabilities in a week, and 40 with no patch

Wordfence’s report for 2 to 8 November, published on 12 November, counts 497 vulnerabilities in 312 plugins and one theme, from 218 researchers. 457 are patched and 40 are not. 21 are rated critical, 118 high, 352 medium and six low. Cross-site scripting leads with 179, followed by missing authorisation with 108, improper privilege management with 29 and code injection with 28. That is down from 549 the week before, and it is now an ordinary week, not a bad one.

One correction to the summaries going round: the 21 are all of the critical entries, not 21 unauthenticated code-execution flaws. Last week’s triage still sorts the list. Unauthenticated and exploited is for today; unauthenticated without the label is for this week; anything that needs a trusted role waits for the maintenance window. Read the 40 unpatched entries in full, because for them the only options are a firewall rule or removal.

Common questions

Common questions about the exploited plugins

Which of the six exploited plugins matter if I only have Contact Form 7?

Contact Form 7 matters on 10 million sites, and its severity depends on your server. Update to 6.2.4 or later. Then confirm that directory listing is off for the uploads tree and that PHP does not execute there; with both in place the flaw leaves junk files rather than a webshell. Look in wp-content/uploads for files with PHP-family extensions, double extensions or a new .htaccess, created since early October.

Elementor is on the exploited list. How worried should I be?

Update to 4.3.6 and you are done with this one. It is a reflected cross-site scripting flaw, so it needs a logged-in user, ideally an administrator, to open a crafted link; that is why Patchstack rates it medium. On ten million installs some administrators will click, which is why it is being used. Teach the people who log in not to follow unexpected links to their own site.

A plugin I use has no fix. Is deactivating it enough?

For WP Libre Form, CryptoPayment Gateway and WP Duplicate, no. Deactivated plugins’ files usually still sit in the web root, and for upload and AJAX flaws that can be enough. Delete the plugin, look for PHP files in uploads and in the plugin folder first, and for CryptoPayment Gateway rotate the wallet keys it stored.

Why is a file deletion bug rated 10?

Because the file it deletes can be wp-config.php. Without it, WordPress runs its installer, and whoever reaches the installer first can connect the site to their own database, create an administrator and upload code. Treat an unauthenticated deletion as a route to takeover, the same as an upload.

Choose the response path

A plugin on this list was installed while it was vulnerable: choose the response path.

The servers under the sites

Get Apache, HTTP/2 and the rest of the web stack checked on every host.

Best when several servers need the Apache version, the protocols per virtual host and the backported packages verified from the running process, the look-back since 11 November done once, and a written result per host.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when a file-upload plugin left PHP in uploads, wp-config.php went missing, the tampered Quick Page/Post Redirect build turned up, or an account changed hands, and you want every layer removed in one pass.