Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain forms-management-capable account
-
DeliveryCraft malicious serialized XML-RPC payload
-
ExploitTrigger unrestricted object deserialization
-
ExecutionWrite attacker-controlled PHP file
-
ImpactExecute 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.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.
Articles & Coverage 1
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
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.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
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.
More in Forminator Forms
View allAn authenticated user holding the quiz-import capability in the Forminator Forms WordPress plugin (versions 1.57.0 throu
Unauthenticated metadata injection in the Forminator Forms WordPress plugin before 1.57.2.1 allows any visitor who submi
Unauthenticated attackers can bypass the per-visitor voting limit and falsify the submitter address recorded for form en
The Forminator Forms WordPress plugin before 1.38.3 does not sanitise and escape some of its settings, which could allow
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to unauthoriz
Privilege escalation in the Forminator Forms WordPress plugin (all versions before 1.57.1) allows unauthenticated remote
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cro
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Order Repl
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Insecure D
The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site
EUVD-2026-83670
GHSA-h6cq-4ghp-3r32
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB