Critical (9.8) in wpmudev forminator forms – contact form, payment form & custom form builder. EPSS 4.1% estimated probability of exploitation activity in the next 30 days.
The Forminator Forms plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.56.1 via the handle_file_upload function. This is due to insufficient file type validation in handle_file_upload, where the dangerous-extension blocklist performs exact-key matching that is bypassed by pipe-alternative MIME type keys, combined with a public submission handler that trusts attacker-controlled upload field configuration injected via a forged Select field value. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.
Severity
CVSS 3.1
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
4.1%(unchanged from 4.1% a week ago; 6.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-08-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-434Unrestricted Upload of File with Dangerous Type
Show the promptExplain CVE-2026-15748 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-15748?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-15748?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-15748 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
wpmudev:forminator forms – contact form, payment form & custom form builder
Versions
From the CNA's record in the CVE List.
Product
Affected
wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder
through 1.56.1
GitHub PoC
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
yora1928/cve-2026-15748Harbor Check: matches CVE3 stars, Python, created CVE-2026-15748 - Unauthenticated RCE exploit for WordPress Forminator plugin (≤1.56.1). Automated detection, deep crawl, nonce extraction, …
0x4cr/CVE-2026-15748Harbor Check: matches CVE0 stars, Python, created Unauthenticated RCE in WordPress Forminator Forms <= 1.56.1 (CVSS 9.8)
ubaydev/CVE-2026-15748Harbor Check: matches CVE0 stars, Python, created Forminator Forms <= 1.56.1 - Unauthenticated Arbitrary File Upload via Forged Upload Field Configuration