Skip to main content

Contact Form 7 Security Flaw: Check Your Version in a Minute

If your website uses Contact Form 7, go to Plugins, then Installed Plugins, and check it’s on version...

Alex

Alex

CEO

November 9, 2026
5 min read
Security alerts

If your website uses Contact Form 7, go to Plugins, then Installed Plugins, and check it’s on version 6.2.4 or later. Versions 6.2 to 6.2.3 have a file upload vulnerability that needs no login, and it only applies to forms with a file upload field. The fix has been available since 29 October 2026.

WordPress.org lists 10 million active installs for the plugin, but the number of exposed sites is well under that. Its version statistics put 19.29% of active installs on the 6.2 branch, a figure that includes sites already updated to 6.2.4, and the plugin’s default form has no upload field. A form plugin is usually set up once when a site is built, so you may be running this one without knowing its name.

What’s affected

CVE-2026-114432, rated 9.8 (critical) on the CVSS 3.1 scale. The WPScan advisory and the CVE record it published cover versions from 6.2 up to, but not including, 6.2.4. The developer’s 6.2.4 release note says the same: the vulnerability “is seen only in Contact Form 7 6.2 to 6.2.3”. The NVD entry words it as “before 6.2.4” and gives no starting version.

No login is needed. Someone can submit a file through a form’s upload field, get past the check on its file type, and leave it on the server when it should have been deleted after the submission. WPScan’s title gives the route as an invalid UTF-8 file name, meaning one built from malformed characters.

The form must have a file upload field. After that, the result depends on the web server. On a stock Debian or Ubuntu Apache configuration, which lists directory contents and treats .phar files as PHP, the advisory says the file can be found and executed. That is remote code execution: someone outside the site getting the server to run instructions of their choosing. On other setups, including nginx and Apache with .htaccess overrides enabled, it says the issue is limited to a file written into the uploads folder, which may still be served as active content such as HTML or SVG from the site’s own address. The developer describes the possible targets as forms with upload fields on a server configured to list directory contents publicly.

Versions before 6.2 are outside the range in both the advisory and the release note. The developer recommends 6.2.4 for all users, because its security enhancements apply to every version. It requires WordPress 7.1 and PHP 8.3, so an older site may not be offered it.

On exploitation: the flaw was not in the CISA Known Exploited Vulnerabilities catalogue as of its 6 November release, and CISA’s assessment on the CVE record, dated 8 November, gives exploitation as “none”. No source we checked reports attacks. WPScan says it will publish its proof of concept on 19 November 2026, so that’s the date to beat.

How to check in a minute

  1. Log in to your WordPress admin.
  2. Go to Plugins, then Installed Plugins, and find Contact Form 7.
  3. Read the version under its description. You want 6.2.4 or later. The current release is 6.2.4.1.
  4. To see whether a form takes uploads, open Contact, then Contact Forms, and look in each form for a tag starting [file.

If your site is run by an agency or host, send them this: “Is our Contact Form 7 on 6.2.4 or later for CVE-2026-114432, and do any of our forms have a file upload field?”

What to do if you’re on an older version

Take a backup first if your host doesn’t take one automatically, then click Update Now on the Installed Plugins screen. Enable auto-updates on the same row covers future releases.

The release note lists a change worth testing for. Uploaded files now keep their extension only if it is on a safelist of image, audio and video formats plus PDF and TXT, and anything else has its extension converted. If your form accepts Word documents or zip files, send a test through and check the attachment still opens. A developer can extend the list with the wpcf7_file_extension_safelist filter.

If your site was on an affected version and your server lists directory contents, have someone turn that listing off. As general practice after any serious flaw, and not something the advisory reports, look for files you don’t recognise under wp-content/uploads/wpcf7_uploads and for administrator accounts you didn’t create under Users.

Why one contact form turns into a website problem

This flaw arrived in a feature release. Version 6.2 came out on 5 October and the fix followed 24 days later. The plugin’s WordPress.org changelog entry for 6.2.4 is a link to the announcement with no mention of security, so an owner skimming it had no reason to hurry.

Keeping a site safe means someone reading those notes and acting on them. If that job has no owner for your site, a support retainer covers it, and WordPress development covers the bigger jobs, such as moving an old site onto the WordPress and PHP versions a fix now requires.

Not sure what else is out of date?

Ask for a free mini audit and we’ll email you a score, the three issues costing you most and three quick wins within two working days, or tell us about your site using the form below.

Written by

Alex

CEO

I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.