---
id: "CVE-2026-114432"
page: "https://infrastack.ai/live/CVE-2026-114432"
kind: "vulnerability"
aliases: ["CVE-2026-114432"]
title: "Contact Form 7 plugin: unauthenticated file upload can lead to code execution"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache", "contact-form-7", "nginx", "package", "self-hosted", "wordpress"]
not_affected_if: ["no-file-upload-fields", "version-6.2.4-or-later"]
published_at: "2026-11-08T06:17:04+00:00"
first_seen_at: "2026-11-08T06:46:21+00:00"
updated_at: "2026-11-08T06:47:17+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114432", "first_seen_at": "2026-11-08T06:46:21+00:00"}]
exploit_sources: []
---

# Contact Form 7 plugin: unauthenticated file upload can lead to code execution

Link for people: https://infrastack.ai/live/CVE-2026-114432 (this .md is for agents)

The Contact Form 7 WordPress plugin before 6.2.4 does not check the type or extension of files uploaded through form file fields, and its temporary-file cleanup leaves them on disk. An unauthenticated visitor can plant an arbitrary file on the site, and on a stock Debian or Ubuntu Apache setup that file can be found and executed as PHP, giving remote code execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Contact Form 7 version in the WordPress admin plugins list, or in the plugin header of `wp-content/plugins/contact-form-7/contact-form-7.php`; versions below `6.2.4` are listed as affected.
- Check whether forms on the site use file upload fields.
- Check the web server configuration for directory listing and `.phar` handling on the uploads path.

## Fix

- Contact Form 7 `6.2.4` (fix is the version named in the sources; earlier versions are affected).

## Timeline

- 2026-11-08T06:46:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114432

## From the sources

The Contact Form 7 WordPress plugin before 6.2.4 does not validate the type or extension of files uploaded through a form file field, and a flaw in its temporary-file cleanup leaves the uploaded file on disk, allowing unauthenticated users to upload arbitrary files to the site. On a stock Debian or Ubuntu Apache configuration, which lists directory contents and maps .phar to the PHP handler, the stored file can be located and executed, leading to Remote Code Execution. On other configurations, including nginx and Apache with .htaccess overrides enabled, the issue is limited to an arbitrary file written into the uploads directory, which may still be served as active content such as HTML or SVG from the site's own origin.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_