CVE-2026-114432 · Package
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 8, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running Contact Form 7 before 6.2.4 with a form that includes a file upload field. Exposure to code execution is highest on stock Debian or Ubuntu Apache hosts where directory listing is on and .phar maps to PHP; nginx and Apache with .htaccess overrides limit the impact to files written into the uploads directory that may be served as active content such as HTML or SVG. Sites without upload fields on their forms are not affected.
Not affected if no-file-upload-fields, version-6.2.4-or-later
Who cares apache, contact-form-7, nginx, self-hosted, wordpress
wp-content/plugins/contact-form-7/contact-form-7.php; versions below 6.2.4 are listed as affected..phar handling on the uploads path.6.2.4 (fix is the version named in the sources; earlier versions are affected).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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.