Skip to main content

Forminator Forms CVE-2026-15748

| EUVDEUVD-2026-60569 CRITICAL
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-08-18 Wordfence GHSA-3p88-69p6-f6mj
9.8
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Locate public Forminator form
  2. Delivery
    Forge Select value to inject upload config
  3. Exploit
    Submit file with pipe-alternative MIME key
  4. Execution
    Bypass extension blocklist, write PHP to uploads
  5. Persist
    Request uploaded script
  6. Impact
    Execute code as web server user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target WordPress site runs Forminator Forms ≤1.56.1 with at least one publicly reachable form (default deployment for a plugin whose purpose is public contact/payment forms). The attacker must forge a Select field value to inject upload-field configuration into the public submission handler and craft an uploaded file whose dangerous extension is expressed via a pipe-alternative MIME key (e.g. a composite 'php|...' key) so it bypasses the exact-key blocklist match in handle_file_upload. No authentication (PR:N) and no user interaction (UI:N) are needed. Limiting factors: server-side execution controls that prevent PHP execution in the uploads directory would neutralize the RCE even on a successful write, and sites with no public-facing form or with upload fields removed are not exploitable; successful code execution runs with the privileges of the web server user.

Impact

This is a genuine top-priority issue, not a high-CVSS-but-low-real-risk case. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with high impact to confidentiality, integrity, and availability, which aligns cleanly with the described unauthenticated-to-RCE chain - the signals are internally consistent rather than conflicting. No EPSS score, CISA KEV listing, or SSVC decision data was provided in the input, so exploitation-probability and automatability cannot be quantified here; this is a data gap, not evidence of low risk. Given that Forminator is a widely installed WordPress plugin and file-upload-to-RCE bugs are historically weaponized quickly once details circulate, even a mid-sized municipal IT team in ustka should treat this as urgent and patch on an emergency basis rather than waiting for a KEV listing. Absence of a published proof-of-concept lowers the immediate mass-exploitation likelihood but does not reduce the underlying severity.

Exploit ScenarioDerived

An unauthenticated attacker locates a public Forminator form and submits a crafted POST that forges a Select field value to inject an attacker-controlled upload field configuration, then attaches a PHP payload whose MIME/extension key uses a pipe-alternative form that evades the exact-match blocklist. The file is written into the site's uploads area, and the attacker requests the uploaded script to execute code on the server. No public exploit is identified at time of analysis, but the low attack complexity (AC:L) and lack of required authentication or user interaction make this straightforward to weaponize.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 1.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 18, 2026

Unauthenticated arbitrary file upload leading to remote code execution affects the Forminator Forms WordPress plugin (WPMU DEV) in all versions through 1.56.1. The public form-submission handler trusts attacker-controlled upload field configuration injected through a forged Select field value, and the dangerous-extension blocklist in handle_file_upload uses exact-key matching that is bypassed with pipe-alternative MIME type keys, letting an attacker drop an executable PHP file on the server. Reported by Wordfence and carrying a CVSS 9.8, this is a critical, network-reachable flaw with no authentication barrier, though there is no public exploit identified at time of analysis.

RemediationAI

Upgrade Forminator Forms to the first release above 1.56.1 that the vendor marks as fixed; the input data does not include an exact patched version number, so the released patched version is not independently confirmed and administrators should verify the fixed release on the WordPress.org plugin page before deploying. Until patched, apply compensating controls: temporarily deactivate the Forminator plugin if forms are not business-critical, or disable/remove any forms that expose file-upload fields to unauthenticated visitors, accepting the trade-off that legitimate uploads (e.g. application or payment attachments) will stop working. Additionally, configure the web server or WordPress hardening rules to deny execution of PHP within the uploads directory (e.g. an .htaccess/nginx location block preventing script execution under wp-content/uploads), which blunts the RCE outcome even if a malicious file is written, and place a WAF rule in front of the form submission endpoint to inspect for forged Select-field/upload-configuration payloads. Reference the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/263ac05d-f1ca-46e3-a43e-3b45eb8066d4?source=cve) for detection and update guidance.

Affected VersionsENISA

Forminator Forms – Contact Form, Payment Form & Custom Form Builder 0 ≤1.56.1

Affected Packages

euvd forminator_forms_contact_form_payment_form_custom_form_builder no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability lives in Forminator's file-upload field handling (library/fields/upload.php) and its custom-forms front-end submission action (front-action.php). The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type): handle_file_upload validates uploads against a blocklist of dangerous extensions, but the lookup is performed as an exact key match against the MIME-type map. Because WordPress/PHP MIME maps use pipe-alternative composite keys (e.g. 'php|php3|php4'), an entry whose key form does not exactly match a single blocklisted extension slips through validation. This is compounded by a trust-boundary failure in the submission handler, which derives the upload field's configuration from client-supplied data - a forged Select field value lets an unauthenticated submitter inject the upload field configuration itself rather than merely supplying a file to a server-defined field. The affected product is identified in CPE as cpe:2.3:a:wpmudev:forminator_forms_-_contact_form,_payment_form_&_custom_form_builder, a general-purpose form/payment builder plugin.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Unauthenticated network submission handler (AV:N/PR:N/UI:N) with a straightforward blocklist bypass (AC:L) yielding code execution, giving full C/I/A impact on the host.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The Forminator Forms WordPress plugin (WPMU DEV) versions through 1.56.1 contain a critical remote code execution vulnerability exploitable by unauthenticated attackers through file upload fields in public forms. The CVSS 9.8 severity combined with the absence of a vendor patch means all instances remain at immediate risk of server compromise and data breach. Organizations using this plugin require urgent action regardless of current WordPress update status.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) immediately disable file uploads in Forminator form configurations; (2) uninstall the plugin and replace with an alternative form builder (recommended); (3) if retention is required, implement Web Application Firewall rules blocking POST traffic to Forminator endpoints combined with disabling PHP execution in wp-content/uploads directory; (4) enable file integrity monitoring on upload directories and maintain encrypted offline backups separate from production infrastructure.

Threat Intelligence Overview

EPSS Score
1.2%
Top 35% exploitable
Prevalence
High
widely installed WordPress form/payment plugin with large active-install base
Social Media
12
Sightings
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment CIRCL 12 sightings

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 1.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy