Skip to main content

Forminator Forms EUVDEUVD-2026-83670

| CVE-2026-87067 HIGH
Code Injection (CWE-94)
2026-09-20 WPScan GHSA-h6cq-4ghp-3r32
8.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

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

  1. Access
    Obtain forms-management-capable account
  2. Delivery
    Craft malicious serialized XML-RPC payload
  3. Exploit
    Trigger unrestricted object deserialization
  4. Execution
    Write attacker-controlled PHP file
  5. Impact
    Execute arbitrary code on server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

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

Exploitation Conditions

Requires an account holding the Forminator Forms 'forms-management' permission - administrator by default, but exploitable by lower roles only if the site has explicitly delegated that capability through Forminator's own settings. The XML-RPC interface must be reachable, and successful code execution depends on a usable PHP POP/gadget chain being present so the unrestricted deserialization can be leveraged into a file write. Limiting factors: PR:L (authenticated with a specific privileged capability, not anonymous) and AC:H (gadget-chain and XML-RPC dependency). On sites where only administrators hold the permission, real-world risk is materially lower since such users are already highly privileged.

Impact

This is a genuine high-priority issue that warrants prompt patching, but its severity is tempered by the access prerequisite. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H = 8.5) reflects an unrestricted-deserialization PHP object injection reachable over the network through XML-RPC, yielding full C/I/A impact via arbitrary file write and code execution. Two signals raise concern: WPScan (the reporter) states publicly available exploit code exists, and a vendor patch (1.57.2.1) is available. Two signals lower it: PR:L means the attacker must already hold the plugin's forms-management permission (administrator by default, only lower roles if the site explicitly delegated it), and AC:H reflects that successful exploitation depends on a usable POP gadget chain and XML-RPC being enabled. No EPSS score or CISA KEV status was provided, so there is no evidence of active in-the-wild exploitation - this is 'publicly available exploit code exists,' NOT confirmed exploitation. The 'unknown' CPE vendor string and 'Unknown' tag are placeholder junk, not a data conflict about the vulnerability itself. Net: real priority for any site that has delegated the forms-management capability below administrator; lower urgency where only admins hold it, since an admin already has extensive control.

Exploit ScenarioDerived

An attacker who holds (or has been delegated) Forminator's forms-management permission on a WordPress site sends a crafted XML-RPC request containing a serialized payload; because the plugin does not restrict which classes may be instantiated on deserialization, a gadget chain is triggered that writes an attacker-chosen file (e.g., a PHP web shell) and executes arbitrary code. Publicly available exploit code (referenced by WPScan) lowers the practical barrier. AC:H reflects the need for a viable gadget chain and an XML-RPC-reachable endpoint.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 20, 2026

Authenticated code execution in the Forminator Forms WordPress plugin (before 1.57.2.1) lets a user who holds the plugin's forms-management capability abuse unrestricted class instantiation during deserialization of an XML-RPC value, ultimately writing a file of the attacker's choosing and executing arbitrary code on the server. That capability is granted to administrators by default, so sites that have not delegated it through Forminator's own settings are materially less exposed, but any lower role given forms-management can reach the flaw; exploitation also depends on a reachable XML-RPC interface and a usable PHP gadget chain, which is reflected in the high attack-complexity component of the 8.5 CVSS score (PR:L, AC:H). Publicly available exploit code exists, and a vendor patch shipping in 1.57.2.1 is available, so sites running affected versions should upgrade promptly.

RemediationAI

The primary fix is to update Forminator Forms to 1.57.2.1 or later - the vendor-released patched version - which constrains class instantiation during deserialization of XML-RPC input; apply this update through the normal WordPress plugin update path and verify the installed version afterwards. Where an immediate upgrade is not possible, the highest-value compensating control is to restrict the forms-management capability so that only fully trusted administrators hold it, auditing any custom roles or membership plugins that Forminator's settings may have granted it to, since PR:L exploitation is only reachable by accounts possessing that permission. A second control is to disable or block XML-RPC entirely (for example via a security plugin, a web-server rule denying xmlrpc.php, or WordPress filters) because the malicious payload is delivered through that endpoint; the trade-off is that legitimate XML-RPC consumers - the WordPress mobile app, Jetpack, and some third-party publishing tools - will break, so this should be a deliberate decision or scoped by source IP rather than applied blindly. Disabling XML-RPC reduces but does not eliminate risk if the vulnerable deserialization sink is reachable through other entry points, and neither workaround substitutes for the 1.57.2.1 upgrade; a WAF rule targeting POST traffic to xmlrpc.php can add interim coverage but may be bypassed. Note that exploit code is publicly available, so prioritise patching on any site where forms-management has been delegated below administrator and XML-RPC remains enabled.

Affected VersionsENISA

Forminator Forms 1.57.0.7 <1.57.2.1

Affected Packages

euvd forminator_forms fix: 1.57.2.1

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 root cause is an unrestricted PHP object deserialization issue (CWE-94, code injection) inside the WordPress Forminator Forms plugin: when the plugin deserializes a value supplied through an XML-RPC request, it fails to constrain which classes PHP may instantiate. PHP's unserialize() honors attacker-controlled object type names, so without an allowed_classes restriction an attacker can force instantiation of classes present in the plugin or its dependencies and walk a PHP POP/gadget chain (magic methods such as __destruct, __wakeup, or __toString triggering file-write primitives), converting the object injection into an arbitrary file write and then into code execution. The transport is WordPress's XML-RPC endpoint (xmlrpc.php), which must be reachable for the request to be delivered, and the attack surface is gated by the plugin's forms-management capability; NVD's CPE string (cpe:2.3:a:unknown:forminator_forms:*:*:*:*:*:*:*:*) leaves the vendor as 'unknown', so version-based identification should rely on the EUVD range (1.57.0.7 before 1.57.2.1) rather than the CPE. The assessed CVSS:3.1 vector AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H matches the vendor's 8.5 and correctly captures the scope change and the fact that this is authenticated, complexity-limited exploitation rather than a single unauthenticated request.

Know when Forminator Forms 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 (WPScan) PRIMARY 8.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.5 HIGH

Network-reachable via XML-RPC (AV:N); needs a viable gadget chain (AC:H); requires the delegated forms-management capability (PR:L); RCE escaping the app to the host justifies S:C with full C/I/A:H.

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

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

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

Lifecycle Timeline

4
CVSS changed
Sep 20, 2026 - 14:22 NVD
8.5 (HIGH)
Patch available
Sep 20, 2026 - 07:01 EUVD
CVE Published
Sep 20, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 20, 2026 - 06:00 cve.org
HIGH 8.5

DescriptionCVE.org

The Forminator Forms WordPress plugin before 1.57.2.1 does not restrict which classes may be instantiated when it deserialises a value taken from an XML-RPC request, allowing users who hold its forms-management permission to write a file of their choosing and execute arbitrary code. That permission belongs to an administrator by default, and to any role the site has granted it through the Forminator Forms WordPress plugin before 1.57.2.1's own settings, so the issue is reachable well below administrator on sites that use that feature.

Technical POC Analysis

Evidence caveat up front: the supplied source is a WPScan vulnerability record only.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Forminator Forms, a widely deployed WordPress plugin, is affected in all versions prior to 1.57.2.1 by an authenticated remote code execution flaw that lets a user with forms-management privileges write attacker-chosen files and run code on the web server. Because that capability sits with site administrators by default, any compromised, over-privileged, or delegated account with forms management can turn the flaw into full control of the hosting environment. Leadership should care because exploitation code is already publicly available and a successful attack can mean website defacement, theft of customer and employee data, and a foothold from which attackers pivot into connected corporate systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
popular WordPress form-builder plugin, hundreds of thousands of installs but not core
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

62
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

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

CVE-2026-87068 MEDIUM POC
6.6 Sep 20

An authenticated user holding the quiz-import capability in the Forminator Forms WordPress plugin (versions 1.57.0 throu

CVE-2026-87071 MEDIUM POC
5.3 Sep 23

Unauthenticated metadata injection in the Forminator Forms WordPress plugin before 1.57.2.1 allows any visitor who submi

CVE-2026-87070 MEDIUM POC
5.3 Sep 23

Unauthenticated attackers can bypass the per-visitor voting limit and falsify the submitter address recorded for form en

CVE-2024-7052 MEDIUM POC
4.8 Feb 14

The Forminator Forms WordPress plugin before 1.38.3 does not sanitise and escape some of its settings, which could allow

CVE-2024-10402 HIGH
8.8 Oct 26

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to unauthoriz

CVE-2026-19220 LOW POC
3.7 Aug 26

Privilege escalation in the Forminator Forms WordPress plugin (all versions before 1.57.1) allows unauthenticated remote

CVE-2025-3487 MEDIUM
6.4 Apr 17

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro

CVE-2025-0469 MEDIUM
6.4 Feb 27

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro

CVE-2025-5341 MEDIUM
6.4 Jun 05

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro

CVE-2025-3479 MEDIUM
5.3 Apr 17

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Order Repl

CVE-2024-9700 MEDIUM
5.3 Oct 31

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Insecure D

CVE-2024-9352 MEDIUM
4.3 Oct 17

The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site

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