{"api_version":"1","generated_at":"2026-11-08T15:49:09+00:00","cve":"CVE-2026-114432","urls":{"html":"https://cve.report/CVE-2026-114432","api":"https://cve.report/api/cve/CVE-2026-114432.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-114432","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-114432"},"summary":{"title":"Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload via Invalid UTF-8 Filename","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.","state":"PUBLISHED","assigner":"WPScan","published_at":"2026-11-08 06:17:04","updated_at":"2026-11-08 06:17:04"},"problem_types":["CWE-434 Unrestricted Upload of File with Dangerous Type"],"metrics":[],"references":[{"url":"https://wpscan.com/vulnerability/6b0a5d1f-84fb-425f-8d37-ddde5703937c/","name":"https://wpscan.com/vulnerability/6b0a5d1f-84fb-425f-8d37-ddde5703937c/","refsource":"contact@wpscan.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-114432","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114432","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Unknown","product":"Contact Form 7","version":"affected 6.2 6.2.4 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Shinya Murakami","lang":"en"},{"source":"CNA","value":"WPScan","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Contact Form 7","vendor":"Unknown","versions":[{"lessThan":"6.2.4","status":"affected","version":"6.2","versionType":"semver"}]}],"credits":[{"lang":"en","type":"finder","value":"Shinya Murakami"},{"lang":"en","type":"coordinator","value":"WPScan"}],"descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"description":"CWE-434 Unrestricted Upload of File with Dangerous Type","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-08T06:00:29.249Z","orgId":"1bfdd5d7-9bf6-4a53-96ea-42e2716d7a81","shortName":"WPScan"},"references":[{"tags":["exploit","vdb-entry","technical-description"],"url":"https://wpscan.com/vulnerability/6b0a5d1f-84fb-425f-8d37-ddde5703937c/"}],"source":{"discovery":"EXTERNAL"},"title":"Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Upload via Invalid UTF-8 Filename","x_generator":{"engine":"WPScan CVE Generator"}}},"cveMetadata":{"assignerOrgId":"1bfdd5d7-9bf6-4a53-96ea-42e2716d7a81","assignerShortName":"WPScan","cveId":"CVE-2026-114432","datePublished":"2026-11-08T06:00:29.249Z","dateReserved":"2026-10-21T13:35:40.479Z","dateUpdated":"2026-11-08T06:00:29.249Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-08 06:17:04","lastModifiedDate":"2026-11-08 06:17:04","problem_types":["CWE-434 Unrestricted Upload of File with Dangerous Type"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"114432","Ordinal":"1","Title":"Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Uplo","CVE":"CVE-2026-114432","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"114432","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Contact Form 7 6.2 - 6.2.3 - Unauthenticated Arbitrary File Uplo"}]}}}