Contact Form 7 runs on millions of WordPress sites, so it is on a lot of client sites you maintain. Versions 6.2 to 6.2.3 let an attacker upload a file without logging in, through a form that has a file field. The fix is version 6.2.4, released on 29 October 2026. Many sites still had not updated a week later. Here is who is affected, how to check a site in two minutes, and what to do.
What the flaw is
- Plugin and versions: Contact Form 7 6.2, 6.2.1, 6.2.2 and 6.2.3. Fixed in 6.2.4. Versions 6.1.x and older are not listed as affected.
- Type: unauthenticated arbitrary file upload, through a crafted (invalid UTF-8) file name sent to the plugin’s REST endpoint.
- Severity: scores differ. Wordfence rates it CVSS 9.8, Patchstack 8.1 and WPScan 7.5. The lower scores reflect that uploads land in a folder with a random name.
- Exploitation: as of 5 November, the plugin author and Wordfence reported no confirmed attacks. Patchstack expects exploitation. Treat it as urgent anyway: the fix is small and the plugin is everywhere.
Who is affected
A site is exposed when all three are true: Contact Form 7 is on 6.2 to 6.2.3, at least one published form has a file upload field ([file] or [file*]), and the site has not been updated to 6.2.4. The risk is highest on servers that list directory contents, because the random upload folder is then easy to find.
Check a client site in two minutes
- In wp-admin, go to Plugins and look at the Contact Form 7 version. Or with WP-CLI:
wp plugin get contact-form-7 --field=version - If it is 6.2 to 6.2.3, check whether any form uses a file field:
wp post list --post_type=wpcf7_contact_form --fields=ID,post_title,post_content | grep -i "\[file" - Open
https://clientsite.example/wp-content/uploads/in a browser. If you see a file list instead of an error or empty page, directory listing is on.
What to do now
- Update Contact Form 7 to 6.2.4 (or newer) on every site. Take a backup first, as with any update.
- Send one test submission on each form with a file field and check that the email arrives, with the attachment.
- Look in
wp-content/uploads/wpcf7_uploads/and the rest ofwp-content/uploads/for files that should not be there, especially.php,.phtmlor.phar:
find wp-content/uploads -type f \( -name "*.php" -o -name "*.phtml" -o -name "*.phar" \) -newermt "2026-10-01"
- Turn off directory listing (Apache:
Options -Indexes; Nginx:autoindex off;) and block PHP execution inwp-content/uploads/. - Found something suspicious? Take the site offline, restore a backup from before the file appeared, then rotate the WordPress salts, admin passwords and database password. Do not just delete the file and move on.
How Verploy helps
Verploy flags known plugin vulnerabilities on every connected site, grouped, with a link to the source record, so a flaw like this shows up as one list instead of forty logins. Every update is checked. Risky ones tested on a copy first, with a backup before anything goes live. A form plugin is exactly where you want that: the update is small, but a broken form means leads that never arrive.
Source: Contact Form 7 6.2.4 release notes, contactform7.com (29 October 2026); WPScan entry “Contact Form 7 6.2 – 6.2.3 – Unauthenticated Arbitrary File Upload via Invalid UTF-8 Filename”, wpscan.com (5 November 2026); Wordfence Intelligence and Patchstack scores as reported on 5 November 2026. Checked 9 November 2026.
Want to see which client sites are exposed, in one list?
Every update is checked, and the risky ones are tested on a copy first. Start free, no credit card.