Skip to main content
CVE-2026-114432VulnerabilityPublished

The Contact Form 7 WordPress plugin before 6.2.4 does not validate the type or extension of files uploaded through a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-114432· High

Not known to be exploited : upgrade to 6.2.4 soon.

Data as of 8 Nov 2026, 08:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 6.2.4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade Contact Form 7 (WordPress plugin) to 6.2.4.

Affected software

ProductAffectedFixed in
Contact Form 7Affected
  • >=6.2 <6.2.4
Fixed in
  • 6.2.4

AI-suggested

Upgrade the Contact Form 7 WordPress plugin to version 6.2.4 or later, where this vulnerability is fixed. Until upgraded, restrict directory listing and disable execution of uploaded files in the uploads directory via web server configuration to reduce risk.

Description

The Contact Form 7 WordPress plugin versions before 6.2.4 contain a vulnerability where the plugin does not validate the type or extension of files uploaded through form file fields. Additionally, a flaw in the temporary-file cleanup process leaves uploaded files on disk. This allows unauthenticated users to upload arbitrary files to the site. On certain server configurations, such as stock Debian or Ubuntu Apache setups that list directory contents and map .phar files to the PHP handler, this can lead to remote code execution. On other configurations, including nginx and Apache with .htaccess overrides, the impact is limited to arbitrary files being written to the uploads directory, which may still be served as active content like HTML or SVG from the site's origin.

References

Community reviews

Loading reviews…