WordPress Form Plugin Security: How to Vet a Forms Plugin
Upload bugs and tampered updates hit WordPress form plugins in 2025 and 2026. 10 checks for WordPress form plugin security before you install one.
How do you know a form plugin is safe before you put it on a client’s site? Most of us look at the install count and the star rating, and neither one tells you much about WordPress form plugin security. A form is the one part of a site built to accept input from anyone on the internet, so a weak plugin there can cost you far more than spam.
Our advice is to check 5 things instead:
- how fast the plugin patches
- whether the vendor has a way to report bugs
- how it handles file uploads
- what it stores
- how its updates reach your site
No form plugin is simply secure. Every popular one named in this article has a security bug or a tampered release on its record. So what you are really choosing is how a plugin fails and how fast its vendor fixes it.
A claim from November 2026 shows why the checking matters. A developer wrote on X that every American football club in the Netherlands had been hacked through a form on a WordPress site. The confirmed breach was at a hosted membership system, and no official source has blamed WordPress or a form. The claim was still easy to believe. In 2025 and 2026, form plugins were hit from both ends: through bugs in what they accept and through tampering with how the plugin itself arrives.
We make Core Forms, a WordPress form plugin, so we have a stake in this topic. The checks below apply to our plugin as much as to anyone else’s, and we run them on it near the end.

Why Form Plugins Are a Target
A form plugin does much more than draw fields. On most sites it also runs all of these, and an attacker can reach each one:
- A public endpoint. The form posts to
admin-ajax.phpor a REST route that works without a login. - File uploads. Files from strangers land in a folder on your server.
- Stored entries. Names, emails and messages sit in your database, and a leak of those is a breach even when no code runs.
- Merge tags and shortcodes. The plugin reads what a visitor typed and turns parts of it into output.
- Integrations. Payment, CRM and email connections mean stored API keys.
- The entries screen. An admin opens what a stranger submitted, so a script hidden in an entry runs in the admin’s browser.
The wider numbers explain why WordPress form plugin security deserves the time. Patchstack’s State of WordPress Security in 2026 counted 11,334 new vulnerabilities across WordPress in 2025, and 91% of them were in plugins. The report doesn’t count form plugins as a separate group, so we can’t give you their share.
Two figures from the same report matter more when you pick a plugin. 46% of the vulnerabilities had no fix from the developer by the time they became public. For the most heavily exploited ones, the weighted median time to the first attack was 5 hours.
So speed matters more than a clean record. A plugin that patches within a day and says so plainly is a safer choice than one with no public bugs because nobody has looked.
Form Plugin Incidents From 2020 to 2026
The WordPress form plugin vulnerabilities and incidents below fall into four types, and each type maps to a check later in this article. We’ve grouped them by how the plugin failed instead of by brand, because nearly every well-known form plugin is on the list.
| How it failed | Plugin | Year | Login needed | Fixed in |
|---|---|---|---|---|
| File handling | Contact Form 7 | 2020 | No | 5.3.2 |
| File handling | Everest Forms | 2025 | No | 3.0.9.5 |
| File handling | Forminator | 2025 | No | 1.44.3 |
| File handling | Super Forms | 2026 | No | 6.3.314 |
| File handling | Elementor Pro forms | 2026 | No | 4.2.2 |
| Injection | Ninja Forms | 2022 | No | 3.6.11 |
| Injection | Fluent Forms | 2025 | Subscriber | 6.1.2 |
| Injection | Formidable Forms | 2026 | No | 6.35 |
| Missing permission check | WPForms | 2024 | Subscriber | 1.9.2.2 |
| Tampered package | Gravity Forms | 2025 | Not applicable | 2.9.13 |
| Tampered package | Fluent Forms Pro | 2026 | Not applicable | 6.2.10 |
File Uploads and File Handling
A file upload field lets a stranger write to your server. In 4 of these bugs the stranger could upload code, and in the fifth they could delete files.
- Contact Form 7, December 2020. A filename with special characters got past the plugin’s sanitization, so an uploaded file could run as a script. The plugin had more than 5 million installs, and version 5.3.2 shipped as an urgent security release.
- Everest Forms, February 2025. CVE-2025-1128 let anyone upload, read and delete files on a site. The plugin had about 100,000 installs, and the bug scored 9.8 out of 10.
- Forminator, July 2025. CVE-2025-6463 let a visitor put a file path inside a submission. The plugin deleted that file when an admin later deleted the entry, and losing
wp-config.phpthat way can lead to a full takeover. - Super Forms, 2026. The plugin didn’t check file types, so anyone could upload PHP. Wordfence saw attacks from July 14 and blocked more than 250,000 attempts, as The Hacker News reported.
- Elementor Pro, August 2026. An attacker could send an empty file first and a PHP file second to get past the Form widget’s upload check. Version 4.2.2 fixed it on August 19, and attacks started the same day. Only sites with a published form that had a File Upload field were exposed.
If your form accepts uploads, upload handling is the first thing we’d vet.
Injection Through Form Logic
A form plugin reads what a visitor typed and acts on it. Injection bugs live in that step.
- Ninja Forms, June 2022. A flaw in merge tags let anyone inject code without a login. The plugin had more than 1 million installs, and there were signs of attacks in progress. WordPress.org pushed the fix as a forced update.
- Fluent Forms, September 2025. CVE-2025-9260 let any logged-in Subscriber inject a PHP object and read files on the server. The first patch caused a fatal error, so 6.1.2 is the version to be on.
- Formidable Forms, 2026. CVE-2026-19857 let visitors run shortcodes, but only on sites where the owner had added a particular token to a form’s custom HTML. It is rated 4.8, which is medium.
The Formidable bug shows that the risk from one flaw can depend on how you set the plugin up.
Missing Permission Checks
A handler can confirm that a request comes from a logged-in user, or from an admin screen, without checking what that user is allowed to do.
WPForms had this problem in December 2024. CVE-2024-11205 let any Subscriber refund payments and cancel subscriptions on sites running versions 1.8.4 to 1.9.2.1. About 6 million sites had the plugin installed.
That bug and the Fluent Forms one above needed only a Subscriber account. So open user registration plus a form plugin with weak permission checks is a bad combination.
Tampered Updates
In the last two cases the attacker tampered with the package on its way to the site and left the plugin’s own code alone. That is what people mean by a WordPress plugin supply chain attack.
- Gravity Forms, July 2025. Copies of 2.9.11.1 and 2.9.12 downloaded by hand from the vendor’s site on July 9 and 10 carried malware. So did Composer installs of 2.9.11.1. The malware blocked updates, called an outside domain and tried to add an admin account. Updates delivered through the dashboard were clean, and the vendor’s notice names 2.9.13 as the safe version.
- Fluent Forms Pro, July 31, 2026. For about 5 hours, an old update server served a tampered 6.2.7. In the vendor’s words, that server “should have been switched off a long time ago”. About 295 customers downloaded it, and sites with auto-updates turned on were included. The incident post describes a backdoor, admin access with no password and scheduled tasks that kept working after the plugin files were replaced.
The vendor’s response is the part we’d study. About 3 weeks later, Fluent Forms Pro 6.2.13 began refusing any update that isn’t signed with a key kept off the vendor’s licensing server, build machine and CDN. The vendor also publishes checksums for its files.
Form plugins weren’t singled out. MalCare’s timeline of compromised updates lists several other premium plugins in 2026, including a case where attackers bought a plugin company and shipped a backdoor in a routine update.
Keeping everything updated is still necessary. It is no longer enough on its own, and it is wise to know how a plugin’s updates are delivered and verified.
When the Form Plugin Is Not the Problem
Some breaches that seem to involve a form start somewhere else. PHP2Shell is a pair of bugs in PHP itself, published on October 21, 2026, that let an attacker run code without logging in.
The PHP Foundation fixed them in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. CISA added them to its list of exploited vulnerabilities 5 days later, and Calif’s write-up confirms the attack against WordPress 7.1.2. No plugin can protect a site from a bug in the language underneath it.
That brings us back to the Dutch clubs. The post on X guessed at PHP2Shell and a WordPress form, and its author said in her next post that it was more likely someone probing. This is what the official notices support:
- Confirmed: an unknown attacker used a flaw in AllUnited’s own software on the evening of November 9, 2026. The attacker copied member data for every association that uses it. AllUnited found the leak the next day and closed it, and NOS reported the breach.
- Also confirmed: the notice that clubs send to members lists names, addresses, birth dates and bank account numbers, plus login details for members who had an account. The Dutch American football federation’s site names AllUnited’s system for member and team administration.
- Not confirmed: that WordPress, a form or PHP2Shell was involved. None of those notices says so.
Our advice is to check your own stack before blaming or swapping a plugin. That means the PHP version, the host and every hosted service that holds your members’ data.
How to Vet a WordPress Form Plugin
These 10 checks are our WordPress form plugin security checklist. They need no special tools, and only one of them needs you to read code. We’d run them before installing a form plugin and again once a year.
Vulnerability History
A bug on the record is normal, and how the vendor handled it tells you more than the bug does.
- Where to look: the plugin’s pages on Wordfence Intelligence, the Patchstack database and WPScan.
- What to read: the severity, whether the attacker needed a login and how long the fix took.
- Red flags: the same kind of bug twice, an entry with no fix or a fix the changelog never mentions.
- Good sign: a release labeled as a security fix on the day it ships, the way Contact Form 7 labeled 5.3.2.
Disclosure Process
Researchers report bugs to the vendors who make it easy.
- Where to look: a
security.txtfile, a security page or a listing in the Wordfence Bug Bounty Program or Patchstack’s free managed disclosure program. - Red flag: the only way to report a bug is the sales contact form.
Update Cadence and Changelog
A changelog tells you whether anyone is still looking after the code.
- Where to look: the last-updated date, the “tested up to” WordPress version and the wording of past security fixes.
- Red flags: no release in 12 months for a plugin that handles uploads or payments, or a vague “minor fixes” line right after a CVE was published.
Update Delivery
Free plugins arrive through the WordPress.org directory. Premium plugins arrive from the vendor’s own server, which is the part that failed in both tampered-package cases.
- Questions for the vendor: Are update packages signed and verified on the site before they install? Are checksums published? Who can push a release?
- Red flags: zip files sent as email links, and nulled or “GPL club” copies. We’d never install either.
Auto-updates help and hurt here. A delay of one day would have avoided a 5-hour tampering window. It would also leave a site open in the first hours after a bug goes public, which is when attacks start. Our advice is to keep auto-updates on for most sites. A delay makes sense only where someone reads the vendor’s security notices every day.
Upload Handling
This check matters only if your forms accept files. If they do, these are the things we’d confirm:
- File types checked on the server against an allowlist, by extension and by content, and not only in the browser.
- Storage outside the web root or in a folder where PHP can’t run, with randomized filenames.
- Limits on file size, and an option to send files to outside storage.
- A test on staging: a
.phpfile and a double-extension file such asphoto.php.jpgsubmitted through the form. The test shows where each file lands and whether a browser can open it.
After the Elementor Pro attacks, site owners were told to look for PHP files in the form’s uploads folder. That holds for every form plugin, since a .php file in an uploads folder is a sign of compromise. Our guide to file uploads in WordPress forms covers the settings in more detail.
Code Hygiene
This check is for developers. The handlers to read first are the ones a logged-out visitor can reach, and a search of the plugin for wp_ajax_nopriv_ and register_rest_route finds them.
- Nonces on submissions and admin actions, as the WordPress nonces documentation describes.
current_user_can()on every AJAX and REST handler. A check for a logged-in user or an admin screen is weaker than a capability check, and that gap was the WPForms bug.permission_callbackset to a real check, never__return_true, on any REST route that reads or changes entries.- Sanitized input and escaped output, with
$wpdb->prepare()on every query. - No
unserialize()on anything a visitor sent. The Ninja Forms and Fluent Forms object injection bugs both came from that.
Spam and Abuse Controls
A form with no limits gets used to relay mail, flood entries and probe the endpoint. That makes spam control part of a secure WordPress contact form.
A plugin should offer these, ideally per form:
- a honeypot field
- a time-based check
- rate limiting
- a CAPTCHA option such as Turnstile, hCaptcha or reCAPTCHA
Our CAPTCHA comparison covers the tradeoffs, and the math CAPTCHA guide explains what a weak CAPTCHA costs in accessibility.
Data Storage and Retention
Data you never stored can’t leak. The AllUnited breach is a reminder of that, because the damage there was the member records themselves.
- Entry storage: whether you can turn it off for a form that only needs to send an email.
- Retention: whether entries can delete themselves after a set number of days.
- Personal data requests: whether you can export and erase one person’s entries.
- Location: whether files and entries live in the database, the uploads folder or a third-party service. Our article on where WordPress stores form submissions shows how to find out.
Integrations and Webhooks
Every connection to another service adds a stored secret and a handler.
- API keys: how the plugin stores them and who can read them in the admin.
- Webhooks: whether outgoing requests are signed, so the receiving system can verify the signature.
- Add-ons: whether integrations are separate pieces you can leave uninstalled. Fewer active add-ons means fewer handlers an attacker can reach.
Vendor and Ownership
The last check is about the people behind the plugin, because whoever can push its next release can reach your site.
- Ownership: who owns the plugin now, and whether it changed hands recently. The acquisition case in MalCare’s timeline started with a sale.
- Past incidents: how the vendor told customers. Gravity Forms and WPManageNinja both published detailed notices with the exact files to look for. That openness is a good sign even after a bad event.
Hardening a Form After Installing It
Several of the bugs above worked only when a specific feature was switched on. So the cheapest hardening is to turn off what the form doesn’t need.
These are the steps we’d take on any site with a form:
- No upload fields unless the form needs them, and a short list of allowed file types when it does.
- No PHP execution in
wp-content/uploads, set with a server rule. - Closed registration when the site doesn’t need user accounts. That removes the Subscriber-level bugs.
- Entry storage off, or a retention period, on forms that only need to send an email.
- A firewall as a second layer. It can’t be the only one, because Patchstack’s test of hosting-company defenses found that only 26% of attacks were blocked.
- PHP and WordPress core patched along with the plugins, since a bug like PHP2Shell sits below all of them.
- Offsite backups with a tested restore. Gaurav Tiwari’s guide to WordPress backup plugins covers the setup.
- Alerts for new admin users, changed files and unexpected files in
mu-plugins.
What to Do After an Incident
If your form plugin is named in an advisory, updating is the first step, and it is usually not enough. Both tampered packages could leave something behind that an update doesn’t remove, such as an extra admin account.
This is the order we’d follow:
- The vendor’s advisory first. It lists the exact files, database rows and scheduled tasks to look for.
- A clean copy of the plugin. WPManageNinja’s instructions say to delete the plugin folder instead of deactivating it, and to install a fresh copy at the end.
- A search for what stays behind: unknown admin users, PHP files in
uploads, files inmu-pluginsyou didn’t put there and scheduled tasks you don’t recognize. - A restore from a backup taken before the incident when you aren’t sure the cleanup is complete. Gravity Forms called that the most reliable route.
- New passwords, salts and API keys after the cleanup. Rotating them on a site that still has a backdoor hands the new ones over too.
- A notice to the people affected if personal data may have leaked. Where GDPR applies, the regulator generally has to be told within 72 hours of the site owner learning about the breach.
Where Core Forms Fits
Core Forms is our own form plugin, so we’d ask you to judge it with the same checks. This is where it stands today:
- Uploads: each file upload field has its own size limit and a MIME-type check.
- Spam and abuse: a honeypot, Cloudflare Turnstile, reCAPTCHA v3, Akismet, a math CAPTCHA and a blocklist are built in. Each form can also cap submissions per IP address per hour.
- Stored data: submissions go to the plugin’s own database table, and a per-form setting turns saving off.
- Webhooks: outgoing webhooks carry a SHA-256 signature and a timestamp, so the receiving system can reject a forged request.
- Disclosure: our security policy says how to report a bug and what happens after a report, and the site publishes a
security.txtfile. We don’t run a paid bug bounty.
We’d rather you test this than take our word for it. The staging upload test from the checklist works on Core Forms the same way it works on any other plugin.
Which Form Plugin Should You Choose?
Our answer is the smallest plugin that does the job, from a vendor with a visible disclosure process and a fast patch record, with the unused features turned off. The rest depends on what the form does:
- A simple contact form: almost any maintained plugin is fine. A form with no uploads, payments, stored entries or logins gives an attacker very little, and you can even build a contact form without a plugin.
- File uploads: upload handling decides it, and the staging test comes before anything else.
- Payments: permission checks decide it, because a payment bug costs money the same day.
- Logged-in users or open registration: every Subscriber-level bug applies to you, so patch speed matters most.
- An agency with many sites: update delivery matters most, because one tampered package reaches every site at once.
We won’t rank the brands by safety, because every one in the table has had a bug or an incident. For features and pricing, our comparison of WordPress form plugins covers that side.
We also wouldn’t rule out Fluent Forms Pro or Gravity Forms because of their incidents. Both vendors published detailed notices, and WPManageNinja changed how its updates are verified within weeks. How a vendor responds tells you more than how many incidents it has had.
FAQ
Is Contact Form 7 safe to use?
Its 2020 upload bug was fixed in 5.3.2, in a release the developer marked as urgent. We’d keep it updated, leave file upload fields off unless a form needs them and read its current entries on Wordfence and Patchstack before deciding.
Is Fluent Forms safe after the 2026 incident?
The incident was specific. A tampered copy of Fluent Forms Pro 6.2.7 was served from an old vendor server for about 5 hours on July 31, 2026, and the vendor now signs its updates. That is separate from the 2025 object injection bug in the free plugin, which 6.1.2 fixed.
Can a contact form get a WordPress site hacked?
Yes. Upload and injection bugs in form plugins have been used to run code on sites, and a permission bug can let a low-level user do what only an admin should. Most of these needed an outdated version or a feature that was switched on, such as a file upload field.
Do I need a security plugin if my form plugin is updated?
A firewall and file monitoring help in the gap between a bug going public and the patch reaching your site. They also help you spot leftover files after an incident. They don’t replace updates or a patched PHP version, and Gaurav Tiwari’s list of WordPress security plugins compares the main options.
Are premium form plugins safer than free ones?
Not automatically. Patchstack found that premium components had 3 times more known exploited vulnerabilities than free ones in 2025, and both tampered-package incidents in this article hit premium builds.
How often should I check my form plugin again?
Once a year, after any change of ownership and whenever a CVE is published for it.
Final Remarks
If you’re still unsure about the form plugin you already run, we’d let its record decide. Its pages on Patchstack and Wordfence show how the last 2 bugs were handled, and the next one will probably be handled the same way.
After that, we’d turn off every form feature the site isn’t using today.