April 2026 WordPress Vulnerability Roundup: Ninja Forms, Kali Forms, and Perfmatters Under Active Exploitation
Four April 2026 plugin CVEs in Ninja Forms File Uploads, Kali Forms and Perfmatters: versions, severity, and whether each is fixed as of 15 Nov 2026.

Three plugin vulnerabilities defined the first half of April 2026: a critical file upload bug in the Ninja Forms File Uploads add-on (CVE-2026-0740), a critical remote code execution bug in Kali Forms (CVE-2026-3584), and two Subscriber-level file bugs in Perfmatters (CVE-2026-4350 and CVE-2026-4351). Fixes exist for all of them today. If you run any of these plugins, update to the current release, then check the site for files dropped before you patched. We checked every item below against published advisories on 15 November 2026.
This page stays an April 2026 roundup, so the dates, versions and exploitation figures describe that month. Where something has changed since, we say so in a separate line. We also corrected several claims in the first version of this post, and we list them near the end so you can see what changed.
What was disclosed in April 2026, and is there a fix today?
This table is the whole post in one view. Severity is the CVSS 3.1 base score published with the CVE. “Fix today” means a patched release exists as of 15 November 2026.
Plugin | CVE | Severity | Public disclosure | Affected versions | Fixed in | Fix today? |
|---|---|---|---|---|---|---|
Ninja Forms File Uploads (paid add-on) | 9.8 Critical, unauthenticated | 6 April 2026 | 3.3.26 and earlier | 3.3.27 (3.3.25 was only a partial fix) | Yes. Current release 3.3.37 (2 November 2026) | |
Kali Forms | 9.8 Critical, unauthenticated | 20 March 2026, mass exploitation 4 to 10 April | 2.4.9 and earlier | 2.4.10 | Yes. Current release 2.4.32 (9 November 2026) | |
Perfmatters (file deletion) | 8.1 High, Subscriber and above | 3 April 2026 | 2.5.9.1 and earlier | 2.6.0 is the first release after the affected range | Yes. Current release 2.7.0 (12 November 2026) | |
Perfmatters (file overwrite) | 8.1 High, Subscriber and above | 10 April 2026 | 2.5.9 and earlier | Outside the affected range from 2.5.9.1; use 2.6.0 or later | Yes, same current release |
Two notes on the table. The Kali Forms bug was disclosed on 20 March, not in April. We keep it here because Wordfence reported the heaviest exploitation in the first half of April, which is when most site owners felt it. And the Perfmatters advisories list affected versions only. The 2.6.0 figure comes from the first release after that range in the Perfmatters changelog, which dated 2.6.0 to 25 March 2026 and notes security updates to code snippet form handling.
None of the four CVEs appears in the CISA Known Exploited Vulnerabilities catalog (catalog version 2026.11.13), even though Wordfence documented real attacks on the first two. The catalog is a short list, so absence from it tells you little about your own risk.
What should I do right now?
Do these in order. The first two take a few minutes; the rest depend on what you find.
- List the three plugins on every site you run and note the versions. Commands are in the next section. A site that never had any of them is not affected by this roundup.
- Update to the current release: Ninja Forms File Uploads 3.3.37 or later, Kali Forms 2.4.32 or later, Perfmatters 2.7.0 or later. Do not stop at the version named in the advisory, because all three plugins have had further security releases since April.
- If an update is not possible today, deactivate the plugin. A deactivated plugin does not load its AJAX or admin handlers, so the endpoints in these advisories are not reachable.
- If the site ran an affected version on or after 20 March 2026, assume it may already have been probed. Look for PHP files in the uploads folder, new administrator accounts and files changed in the exploitation window (commands below).
- If you find anything, change every credential tied to the site, rotate the WordPress salts and restore from a backup taken before 20 March if you have one. Deleting a single shell file rarely ends an incident.
- Add a rule that blocks PHP execution inside wp-content/uploads. It does not fix any plugin bug, but it stops the most common follow-up step after an upload flaw.
- Turn on update notifications for paid plugins, since these do not update from WordPress.org. We cover that in the mistakes section.
How do I check which versions I run?
Run these from the WordPress root with WP-CLI. The first command shows every active plugin with its installed and available version, and the grep narrows it to the three in this roundup. Slugs can differ if a vendor ships its plugin under another folder name, so compare against your own plugin list if nothing prints. Checked on 15 November 2026 against the wp plugin list reference.
wp plugin list --fields=name,status,version,update,update_version --format=table | grep -E "ninja-forms-uploads|kali-forms|perfmatters"To preview an update without applying it, use the dry run. Then update the three plugins by name. Paid plugins such as Perfmatters and the Ninja Forms add-on only update from the command line when your license is active and the vendor’s update feed is reachable, so confirm the version again afterwards.
wp plugin update --all --dry-run
wp plugin update kali-forms perfmatters ninja-forms-uploads
wp plugin deactivate ninja-forms-uploads # only if you cannot update yetPlugin options are documented on the wp plugin update page.
Is Ninja Forms File Uploads CVE-2026-0740 patched?
Yes. Wordfence disclosed the bug on 6 April 2026 and rated it 9.8. The File Uploads add-on did not validate file types in the NF_FU_AJAX_Controllers_Uploads::handle_upload function, so an unauthenticated visitor could upload arbitrary files, including PHP, to the server. The CVE-2026-0740 record says versions up to and including 3.3.26 are affected, that 3.3.25 only partly fixed the problem and that 3.3.27 fixed it fully.
The vendor’s own File Uploads changelog dates 3.3.27 to 16 March 2026. That is three weeks before the public disclosure, so sites that updated promptly in March were never exposed. Sites that waited were. Wordfence reported mass exploitation between 9 and 13 April, with its firewall blocking more than 118,000 attempts, in its post Attackers Actively Exploiting Critical Vulnerability in Ninja Forms File Upload Plugin.
Two details matter for scope. First, this is the paid File Uploads add-on, not the free Ninja Forms core plugin. Press coverage at the time put the exposure at roughly 50,000 sites, which is the add-on’s footprint. Second, the add-on is not hosted on WordPress.org, so it does not appear in the normal update screen unless your Ninja Forms license is active.
Since April the add-on has had more security releases. The vendor changelog lists fixes in 3.3.28 (8 April), 3.3.29 (20 May), 3.3.30 (2 July), 3.3.31 (20 July), 3.3.34 (22 September) and 3.3.37 (2 November). Patchstack’s Ninja Forms File Uploads page also lists later, separate issues such as an unauthenticated file read affecting 3.3.29 and earlier. These are different bugs from the April one, which is why we say to run the current release rather than 3.3.27.
Was the Kali Forms remote code execution bug exploited in April?
Yes, heavily. CVE-2026-3584 affects Kali Forms 2.4.9 and earlier. The form_process function mapped user-supplied field names straight into internal placeholder storage and then called PHP callables on those values, which let an unauthenticated visitor run code on the server. The score is 9.8.
Wordfence said exploitation began on the day of disclosure, 20 March 2026, and that mass exploitation ran from 4 to 10 April, with more than 312,000 blocked attempts in total. The details are in Wordfence’s April write-up. The fix is version 2.4.10, whose changelog on WordPress.org says only keys matching real form fields are now mapped into placeholder data. WordPress.org lists about 10,000 active installs, so this is a small plugin by install count, and a good reminder that small does not mean quiet.
A second, unrelated Kali Forms remote code execution bug followed in the summer: CVE-2026-16144 affects 2.4.20 and earlier, scores 8.1, and needs a form that defines a field named like one of the reserved placeholder keys. WordPress.org shows 2.4.32 as the current release, published 9 November 2026, with a long run of security fixes between 2.4.10 and now. If you patched to 2.4.10 in April and stopped, you are two security bulletins behind.
What could an attacker do with the Perfmatters bugs?
The two Perfmatters bugs need a logged-in account, but only the lowest role. CVE-2026-4350 is a path traversal in the PMCS::action_handler() method. It passed the delete parameter to unlink() without sanitising it, checking capabilities or verifying a nonce, so any Subscriber could delete arbitrary files. The NVD description names wp-config.php, since deleting it pushes WordPress back into the install wizard and can allow a takeover. The score is 8.1.
CVE-2026-4351 is the sibling bug, published 10 April. The same handler passed the snippets array to file_put_contents() when activating or deactivating a snippet, so a Subscriber could overwrite arbitrary files with a fixed PHP comment block. That can corrupt .htaccess or index.php and take a site down. The score is also 8.1.
We found no source reporting active exploitation of either Perfmatters bug, and neither is in the CISA catalog. The first version of this post said otherwise, and that was wrong. The practical risk depends on your registration settings. A brochure site with registration closed has almost no Subscriber accounts to abuse. A membership, community or course site where anyone can sign up has exactly the audience the bug needs. Perfmatters is used on roughly 200,000 sites according to the ZeroPath analysis.
Perfmatters has shipped further security fixes since April, including capability checks in 2.6.7 and prepared SQL in 2.6.9. Patchstack’s Perfmatters page lists later separate issues, including an unauthenticated file read affecting 2.6.4 and earlier. Run 2.7.0 or later.
How do I know whether my site was already hit?
Patching closes the door. It does not remove anything that came through before you patched. Run these checks on any site that had an affected version after 20 March 2026. They are read-only, so run them first and decide what to do after.
PHP files in the uploads folder
A normal WordPress site does not keep executable PHP in wp-content/uploads. Any hit deserves a look.
find wp-content/uploads -type f \( -name "*.php" -o -name "*.phtml" -o -name "*.phar" \) -lsFiles changed during the exploitation window
This lists PHP files modified between 20 March and 20 April 2026 and skips the cache folder. It uses GNU find, so on macOS install findutils or run it on your Linux host. Compare the result against your own deploy and update history.
find . -type f -name "*.php" -newermt "2026-03-20" ! -newermt "2026-04-20" -not -path "./wp-content/cache/*" -lsAdministrator accounts you do not recognise
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --orderby=user_registered --order=DESCUnexpected scheduled tasks and must-use plugins
Attackers like persistence that survives a cleanup. Scheduled events and the mu-plugins folder are two of the usual places.
wp cron event list --fields=hook,next_run_relative,recurrence --format=table
ls -la wp-content/mu-plugins/Core and plugin file integrity
These compare your files with the official WordPress.org checksums. They cover core and plugins hosted on WordPress.org, such as Kali Forms. They cannot check paid plugins like Perfmatters or the Ninja Forms add-on. See the verify-checksums reference and the core verify-checksums reference.
wp core verify-checksums
wp plugin verify-checksums kali-formsServer logs
If you have access logs from March and April, look for POST requests to admin-ajax.php and to your form endpoints followed by requests to a new PHP file under uploads. Wordfence named 209.146.60.26 as the busiest source in the Kali Forms wave, so it is worth a grep, although attackers rotate addresses and a clean result proves little.
grep "209.146.60.26" /var/log/nginx/access.log* | headIf any of these checks turns up something, treat the site as compromised. Rotate every password tied to it (WordPress, hosting, SFTP, database, email), regenerate the salts, and restore from a backup that predates 20 March if you can.
wp config shuffle-saltsThe salts command is documented on the wp config shuffle-salts page. It logs everyone out, which is the point. For a wider walkthrough of a full site audit, see our guide to auditing WordPress site security in five minutes.
How do I stop PHP running in the uploads folder?
All three of these bugs were dangerous because a written file could be executed. Blocking execution in the uploads folder does not fix a plugin, and it will not help against a Perfmatters deletion. It does cut off the typical next step after an upload flaw. Checked against Apache 2.4 and nginx syntax on 15 November 2026.
For Apache 2.4, put this in wp-content/uploads/.htaccess:
<FilesMatch "\.(?:php|phtml|phar)$">
Require all denied
</FilesMatch>For nginx, add a location block before your general PHP location, because nginx uses the first matching regular expression:
location ~* ^/wp-content/uploads/.*\.(?:php|phtml|phar)$ {
return 403;
}Test it by placing a harmless test.php file in the uploads folder and requesting it. You should get a 403 response. Remove the file afterwards. Our guide to hardening a site that accepts member uploads goes further on server-side controls, and the WordPress file permissions guide covers who should be able to write where.
Why did these bugs happen, and what should plugin developers check?
All four CVEs are the same few mistakes. The upload bug validated nothing about file type. The Kali Forms bug trusted user-supplied keys as internal names. The two Perfmatters bugs ran file operations on request parameters with no capability check or nonce. WordPress gives developers the tools for each one, so this is about skipping them rather than missing them.
- Check a capability with
current_user_can()before any action that changes data or files. Subscriber is a valid logged-in user, so a login check alone is not a permission check. - Verify a nonce with
wp_verify_nonce()orcheck_admin_referer()on every state-changing request, including ones triggered by a GET link. - Validate uploads with
wp_check_filetype_and_ext()andsanitize_file_name(), and use an allowlist of extensions rather than a blocklist. - Resolve any user-supplied path with
realpath()and confirm it sits inside the directory you expect before callingunlink()orfile_put_contents(). - Never map request keys into internal variables or callable names. Accept only keys you defined.
The WordPress security APIs handbook covers each of these. The Ninja Forms changelog shows the cost of an incomplete fix: 3.3.25 sanitised file paths, 3.3.26 widened the extension blocklist, and the full fix only arrived in 3.3.27. When a fix covers one path, test the sibling paths too.
What did the first version of this post get wrong?
We rechecked every claim against the advisories on 15 November 2026 and corrected these. Corrections matter more on a security post, because readers act on it.
- Kali Forms was described as disclosed between 6 and 12 April. Wordfence published it on 20 March, and April was the peak of exploitation.
- Perfmatters was listed as under active exploitation. We found no report of that, so we removed the claim.
- The post said three plugins with millions of combined installs were hit. The affected products are the paid Ninja Forms File Uploads add-on (about 50,000 sites reported), Kali Forms (about 10,000 installs) and Perfmatters (about 200,000 sites). The free Ninja Forms core plugin was not the affected product.
- The Perfmatters bug was described in general terms. The CVE records show it needs a Subscriber account and covers both file deletion and file overwrite.
- The disclosure timeline section described a generic 30-day pattern as if it applied here. It did not: the Ninja Forms fix was out three weeks before disclosure, and the Kali Forms bug was attacked on disclosure day. We removed it.
Common mistakes people report when patching plugin vulnerabilities
These come up repeatedly in vendor changelogs, advisories and incident write-ups. We found few public forum threads about these specific plugins, so each point below links to the primary record we based it on. Checked on 15 November 2026.
- Updating the plugins you can see and forgetting the paid add-on. Ninja Forms File Uploads is a separate paid extension, and the CVE record links to its vendor page rather than to WordPress.org. If the license lapsed or nobody reads that account’s email, the dashboard may never offer the update.
- Stopping at the first version number in the advisory. The Ninja Forms bug had a partial fix in 3.3.25 and a full one in 3.3.27, per the CVE-2026-0740 record. A site on 3.3.25 felt patched and was not.
- Patching after the attack window and assuming the site is clean. Kali Forms exploitation started on 20 March, and the heavy wave ran from 4 to 10 April, per Wordfence. An update on 12 April protected the site from then on and did nothing about a shell dropped on 6 April.
- Treating an authenticated bug as low risk. The Perfmatters bugs need only a Subscriber account, per CVE-2026-4350. On a site with open registration, that is every visitor who fills in a form.
- Reading one CVE and missing the later ones. Kali Forms had a second remote code execution bug (CVE-2026-16144) months after the first, and Patchstack lists further issues for all three plugins. Patching to the version in the April advisory leaves you exposed to later ones.
- Relying on auto-updates alone. The auto-update toggle in WordPress covers plugins that publish an update through WordPress.org or a compatible feed. Premium plugins may or may not, so confirm each one with
wp plugin listafter the fact.
Do I need a scanner or firewall for this?
A scanner will not replace patching, but it can tell you which of your sites run a vulnerable version, which is the hard part once you manage more than a handful. There are good free and paid options, and they overlap more than they differ.
- Wordfence Intelligence publishes the free vulnerability database behind most of the CVEs above, and the Wordfence plugin adds a firewall.
- Patchstack publishes a searchable database and sells virtual patching for known vulnerabilities.
- WPScan offers a database and API that many agencies use to monitor client sites.
- WP Vanguard is our own scanner. Its free surface scan checks a site externally for known CVEs, exposed files, security headers and SSL, and its deep scan looks at server files for malware patterns and core file integrity.
We built WP Vanguard, so weigh that. It fits best if you look after several sites and want one place to see which ones run an outdated plugin. It has real limits. It reports known vulnerabilities from public databases, so it cannot warn you about a flaw nobody has disclosed. An external scan can only see a plugin’s version when the site exposes it, which hides many premium add-ons. The deep scan reads files on the server, so it needs access to the server. And it is a detection tool: it does not patch anything for you, and cleanup after an incident is a separate paid service. If you have two or three sites, WP-CLI and a weekly look at the advisory databases above cover you at no cost.
Frequently asked questions
Which WordPress plugin vulnerabilities were disclosed in April 2026?
The three covered here are Ninja Forms File Uploads (CVE-2026-0740, disclosed 6 April), Kali Forms (CVE-2026-3584, disclosed 20 March and exploited heavily from 4 to 10 April) and Perfmatters (CVE-2026-4350 on 3 April and CVE-2026-4351 on 10 April). For another April disclosure, see our write-up of the Wordfence weekly report on Perfmatters, Ninja Forms and MW WP Form. We did not recheck MW WP Form for this page.
Do I still need to worry about these if I updated in April?
Not about the original bugs, provided you updated to a fixed version. You should still check for files dropped before you patched, and you should move to the current release of each plugin, since all three have had later security fixes.
Is Ninja Forms File Uploads the same as the Ninja Forms plugin?
No. The file upload bug is in the paid File Uploads add-on. The free Ninja Forms core plugin from WordPress.org is a different product with its own advisories.
Can I just delete the plugin instead of updating?
Yes, if you do not need it. Deleting removes the vulnerable code entirely, which is safer than leaving an unused plugin installed. Check for dropped files first, because removing the plugin does not remove a shell that was already uploaded.
Will blocking PHP in uploads protect me from these bugs?
Only from the upload class of bug, and only if the attacker needs to run an uploaded file. It does nothing against the Perfmatters deletion bug. Treat it as one layer next to updating.
How fast should I patch a critical plugin bug?
Treat unauthenticated critical bugs as same-day work. Wordfence reported exploitation of the Kali Forms bug on the day of disclosure, so the window between advisory and attack can be zero.
Where did we get the facts for this roundup?
Every item is tied to a published record. Dates and versions were checked on 15 November 2026.
- CVE-2026-0740, CVE-2026-3584, CVE-2026-4350, CVE-2026-4351 and CVE-2026-16144 on NVD, all assigned by Wordfence.
- Wordfence’s April 2026 posts on the Ninja Forms File Upload and Kali Forms exploitation waves, linked above. Wordfence blocks automated page fetches, so we read those two posts through search excerpts and cite the figures as Wordfence’s.
- Patchstack’s Kali Forms page, Perfmatters page and Ninja Forms File Uploads page for later issues.
- Vendor changelogs: Perfmatters, Ninja Forms File Uploads and Kali Forms on WordPress.org.
- The CISA Known Exploited Vulnerabilities catalog, checked for all four April CVEs.
How do I report a vulnerability I find?
Report it privately. Wordfence, Patchstack and WPScan all run disclosure programs, and they coordinate with the plugin author so a fix exists before details are public. Give a reproduction, the affected versions and the impact, and allow the author time to patch. Publishing details first leaves site owners exposed with no fix to install.
For the wider picture of why patch gaps keep growing, read our piece on how fast AI finds WordPress vulnerabilities compared with how fast fixes ship.
Plugins we build and run
We maintain these ourselves, which is why we can support them on your site.
- BuddyNextThe self-hosted community engine for WordPress
- BuddyXFree community theme, Pro when you outgrow it
- ReignPremium community theme. Add pieces, build anything
- JetonomyCommunity forum and Q&A for WordPress
- EventonomyEvents and RSVPs for WordPress communities
- LearnomyCourses and learning communities on WordPress
- ListoraDirectories and listings your members can browse
- SnipShareCode sharing built for developer communities
- WB Ad ManagerAd placements that turn traffic into revenue
- WP Career BoardA job board your community actually uses
- WP Sell ServicesSell services with offers, orders, and payouts
- MediaVersePhotos, video, and media albums for members
- WB GamificationPoints, badges, and rewards that keep members active
- Product RoadmapPublic roadmaps with voting your users trust
Related Posts

LiteSpeed Cache Vulnerability CVE-2026-93389: Check Your Version and What Was Exposed

Freemius SDK Stored XSS: How to Find Every Bundled Copy on a Client Site (Anything Under 2.13.5)

