Contact Form 7 vulnerability records and how to check your site
File upload recurs in the titles of the Contact Form 7 records.
This page explains their version fields, and where to read the plugin version, forms, additional settings, mail templates and connected services on a site you are authorised to review.
On this page
Contact Form 7 vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 11 records for Contact Form 7. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 6.2.5
Worked out from data retrieved on .
Every affected range listed in this source for Contact Form 7 ends before version 6.2.5.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Contact Form 7 <= 6.2.4 - Authenticated (Editor+) Information Exposure
- Published:
- Last updated:
- Severity:
- Low (CVSS 2.7)
- CVE:
- CVE-2026-120407
Affected versions- All versions up to and including 6.2.4
Patched versions: 6.2.5
Update to at least version 6.2.5.
Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2026-114432
Affected versions- From version 6.2 up to and including 6.2.3
Patched versions: 6.2.4
Update to at least version 6.2.4.
Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
Affected versions- From version 6.2 up to and including 6.2.3
Patched versions: 6.2.4
Update to at least version 6.2.4.
Contact Form 7 <= 6.0.5 - Order Replay Vulnerability
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2025-3247
Affected versions- All versions up to and including 6.0.5
Patched versions: 6.0.6
Update to at least version 6.0.6.
Contact Form 7 <= 5.9.4 - Unauthenticated Open Redirect
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-4704
Affected versions- All versions up to and including 5.9.4
Patched versions: 5.9.5
Update to at least version 5.9.5.
Show 6 older recordsHide the older records
Contact Form 7 <= 5.9 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-2242
Affected versions- All versions up to and including 5.9
Patched versions: 5.9.2
Update to at least version 5.9.2.
Contact Form 7 <= 5.8.3 - Authenticated (Editor+) Arbitrary File Upload
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.6)
- CVE:
- CVE-2023-6449
Affected versions- All versions up to and including 5.8.3
Patched versions: 5.8.4
Update to at least version 5.8.4.
Contact Form 7 <= 5.3.1 - Arbitrary File Upload via Bypass
- Published:
- Last updated:
- Severity:
- High (CVSS 8.1)
- CVE:
- CVE-2020-35489
Affected versions- All versions before 5.3.2
Patched versions: 5.3.2
Update to at least version 5.3.2.
Contact Form 7 <= 5.0.3 - Authorization Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.3)
- CVE:
- CVE-2018-20979
Affected versions- All versions before 5.0.4
Patched versions: 5.0.4
Update to at least version 5.0.4.
Contact Form 7 <= 3.5.2 - Arbitrary File Upload
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
Affected versions- All versions up to and including 3.5.2
Patched versions: 3.5.3
Update to at least version 3.5.3.
Contact Form 7 < 3.7.2 - CAPTCHA Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2014-2265
Affected versions- All versions before 3.7.2
Patched versions: 3.7.2
Update to at least version 3.7.2.
Check Contact Form 7 on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Where Contact Form 7 accepts input
Contact Form 7 is an open source contact form plugin published on WordPress.org by Rock Lobster Inc.
Activating it adds a Contact menu to the admin screen, and the plugin's help text names two ways a form reaches the site: the Contact Form 7 block and, for the classic editor, a shortcode. So a Contact Form 7 vulnerability check has two places to look on a site: the published form and the admin screens behind it.
The plugin's built-in help text names several field types a form can carry, among them file-uploading fields and CAPTCHAs. Each form is edited as parts, including Form, Mail and Additional Settings, and the same help text describes a screen where you manage services that are available through Contact Form 7.
A record title in the history on this page includes the words Authenticated (Editor+), and WordPress documents an Editor as able to publish and manage posts, including other users' posts.
What recurs in the Contact Form 7 vulnerabilities on record
File upload is a theme that returns in this plugin's history.
These three examples all carry Arbitrary File Upload in their titles, with different words around it.
- CVE-2026-114432, whose title ends "Unauthenticated Arbitrary File Upload". Affected: from version 6.2 up to and including 6.2.3. Patched: 6.2.4.
- CVE-2023-6449, whose title ends "Authenticated (Editor+) Arbitrary File Upload". Affected: all versions up to and including 5.8.3. Patched: 5.8.4.
- CVE-2020-35489, whose title ends "Arbitrary File Upload via Bypass". Affected: all versions before 5.3.2. Patched: 5.3.2.
Reading the ranges and patched versions
The two older examples cover every version up to a ceiling, while CVE-2026-114432 starts at version 6.2, so a site on a lower version is outside that record but may be inside an older one. Where a title is listed twice, with a CVE id on only one entry, that is how the source data records it. A patched version tells you which release closed that record, and nothing about later records.
Carrying out each Contact Form 7 check
Go through the read-only checklist on this page as an administrator, opening each screen to read it and leaving without saving.
Where accounts already exist in other roles, ask their holders whether the Contact menu appears for them, and record the answers.
Plugin version
Read the version on the Contact Form 7 row under Plugins > Installed Plugins and note the date. Since WordPress 5.5, administrators can opt in to automatic updates plugin by plugin; record whether that is on here. The gap to the Version field on the plugin's WordPress.org listing is your update status.
Published forms
Open the plugin's list of contact forms and list each form by title, then look through post content and block theme templates for the Contact Form 7 block or its shortcode to see where each is placed. The help text says a duplicated form inherits the original's content under a different ID, so include copies. Note every file-uploading field and CAPTCHA.
Additional settings
Each form has an Additional Settings part, which the help text describes as a place to customise the form's behaviour with code snippets. Copy every line, form by form, note an empty one as empty, and look each line up in the vendor's documentation.
Submission access
The help text says Mail manages the template, headers and message body, that the form sends when users submit it. Record the headers of the Mail and Mail (2) templates, every address in them, and who reads each inbox. If Flamingo, the publisher's message storage plugin, is active, ask the holders of accounts in other roles whether its menu appears for them, and record the answers.
Integration configuration
The help text describes a screen where you manage services that are available through Contact Form 7. It says you may need to sign up for an account with a service first, and would then need to authorise the plugin to access the service with your account.
Find that screen among the plugin's admin pages and list each service set up, the account behind it and who owns it, keeping credentials out of your notes.
Where a Contact Form 7 version match stops
A version match shows whether a known record covers your copy of Contact Form 7.
It does not show whether anyone used the flaw, which is a question for server and access logs, or how the site is configured: which forms accept files, where Mail sends submissions, who can open the Contact menu.
A WordPress security audit adds testing a version match cannot: it starts logged out, calling without a session the REST routes and admin-ajax actions that plugins register for logged-out visitors, tests upload paths with files that are not what their extension claims, and records plugin versions with dated evidence.
Frequently asked questions
Each record has its own affected range and patched versions field: CVE-2023-6449 covers all versions up to and including 5.8.3 and lists 5.8.4 as patched. For one version to move to, read the update guidance at the top of the history.
The publisher's listing for Flamingo, its message storage plugin, says Contact Form 7 does not store submitted messages. With Flamingo activated, that listing says messages are listed and searchable in the admin screen and stored in the site's database, where they may include submitters' personal information.
This history holds the records the source data files under Contact Form 7 itself. Being filed there does not tell you whether a record also applies to Flamingo or another add-on. Flamingo has its own WordPress.org listing and version number. Check it, and any other add-on, as its own row on the Plugins screen.
They say what was reported, which versions it covers and which release closed it. File upload recurs in the titles, which is why the checks note every file-uploading field. The records are not a rating of the plugin, and their number is not a measure in either direction.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 9 of the 11 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Contact Form 7 <= 6.2.4 - Authenticated (Editor+) Information Exposure (CVE-2026-120407)
- Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload (CVE-2026-114432)
- Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload
- Contact Form 7 <= 6.0.5 - Order Replay Vulnerability (CVE-2025-3247)
- Contact Form 7 <= 5.9.4 - Unauthenticated Open Redirect (CVE-2024-4704)
- Contact Form 7 <= 5.9 - Reflected Cross-Site Scripting (CVE-2024-2242)
- Contact Form 7 <= 5.8.3 - Authenticated (Editor+) Arbitrary File Upload (CVE-2023-6449)
- Contact Form 7 <= 5.3.1 - Arbitrary File Upload via Bypass (CVE-2020-35489)
- Contact Form 7 <= 5.0.3 - Authorization Bypass (CVE-2018-20979)
- Contact Form 7 <= 3.5.2 - Arbitrary File Upload
- Contact Form 7 < 3.7.2 - CAPTCHA Bypass (CVE-2014-2265)