Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable Forminator poll/form
-
DeliveryCraft submission with spoofed X-Forwarded-For header
-
ExploitPlugin trusts client header over connecting IP
-
ExecutionBypass per-visitor vote limit / forge stored address
-
ImpactSkew poll results and poison entry records
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication IP-independent access control
|
| Exploitation Conditions | No special conditions or authentication are required - remote unauthenticated exploitation against default configurations of the Forminator Forms WordPress plugin before 1.57.2.1, which unconditionally prefers client-supplied forwarding headers (e.g. X-Forwarded-For) over the real connecting address without verifying the request came from a trusted proxy. Practical limits: to abuse the voting-limit bypass the site must actually host a Forminator poll/voting form, and to forge stored data the attacker only needs any reachable Forminator submission endpoint. Impact is bounded to poll-result manipulation and falsified submitter-address records; there is no code execution, no data disclosure, and no availability impact. Sites that terminate and normalize forwarding headers at a properly configured upstream proxy reduce but do not eliminate the abuse of the attacker-controlled header value reaching the plugin. |
| Impact | This is a genuine but low-severity business-logic and data-integrity flaw, not a system-compromise issue. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3 Medium) correctly reflects a remotely reachable, unauthenticated, low-complexity weakness with no impact to availability. A publicly available exploit exists (WPScan), so exploitation is trivial where a vulnerable Forminator poll or form is exposed - but publicly available exploit code exists is distinct from active exploitation: there is no CISA KEV listing and no EPSS score in the provided data, so real-world exploitation is unproven and this should be treated as opportunistic/nuisance abuse rather than a targeted-compromise priority. The core signal conflict worth flagging: the vendor scored C:L (confidentiality) and the tag says Information Disclosure, but the described impact - voting without limit and choosing the address recorded against every submission - is an INTEGRITY problem (data/result manipulation and log/attribution spoofing), not a confidentiality leak; the C:L rating is difficult to justify from the description. No CVSS attack requirement or scope change is involved. Overall: real, easily exploitable, but bounded impact (poll-result skewing and forged submitter IPs), making it a low-to-moderate remediation priority best resolved by upgrading to 1.57.2.1. |
| Exploit ScenarioDerived | An unauthenticated attacker targets a WordPress site running a Forminator poll and repeatedly submits votes while rotating a spoofed X-Forwarded-For header, bypassing the per-visitor limit to arbitrarily inflate or skew poll results. On form submissions, the attacker sets the forwarding header to any chosen value so the address stored against each entry is falsified, poisoning audit/attribution records. A public exploit is available via WPScan, lowering the skill required to weaponize this. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Unauthenticated attackers can bypass the per-visitor voting limit and falsify the submitter address recorded for form entries in the Forminator Forms WordPress plugin before 1.57.2.1. The plugin prefers client-supplied forwarding headers such as X-Forwarded-For over the actual connecting address without first confirming the request originated from a trusted proxy, so every attacker-controlled request appears to come from a different, self-chosen IP - breaking both the vote-throttling logic and the integrity of stored submission metadata (rated CVSS 5.3, integrity-only impact, no code execution, data disclosure, or availability loss). Publicly available exploit code exists per the WPScan advisory, making this trivially reproducible; it is not reported as confirmed actively exploited (no CISA KEV entry), and exploitation of the voting bypass requires the site to actually host a Forminator poll.
RemediationAI
Vendor-released patch: upgrade the Forminator Forms WordPress plugin to version 1.57.2.1 or later, which stops the plugin from trusting client-supplied forwarding headers unless the request originates from a verified trusted proxy; the fix is documented at https://wpscan.com/vulnerability/3206e88e-5d29-4897-863e-101dc9b33ec5/. Where immediate upgrading is not possible, compensate as follows: terminate and normalize incoming requests at a properly configured upstream reverse proxy that strips client-supplied X-Forwarded-For, X-Real-IP, and Forwarded headers and re-adds only proxy-generated values - the independent assessment notes this reduces but does not eliminate abuse, since any path that reaches the plugin without passing through the proxy still preserves the spoofable header; restrict voting to authenticated users only, which defeats the limit-bypass but degrades anonymous poll participation and does not fix forged submitter records; if poll integrity is not essential, disable the Forminator poll/voting module entirely, accepting loss of that functionality; and audit existing stored submissions for anomalous or high-volume source addresses to gauge prior manipulation, since historical entries may already contain falsified addresses with no other forensic trace. Note that the submitter-address forgery can still be exercised against any reachable Forminator submission endpoint even when polling is disabled, so header sanitization at the edge combined with the 1.57.2.1 upgrade remains the only complete remedy.
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 flaw is a trust-boundary error in how Forminator Forms resolves a visitor's source address within a WordPress deployment. HTTP forwarding headers (X-Forwarded-For, X-Real-IP, Forwarded) are inherently spoofable because they are plain request headers; applications must only honor them when the immediate peer is a known, trusted reverse proxy and should then take the right-most or proxy-appended value rather than the left-most client-supplied one. Forminator before 1.57.2.1 does not perform that proxy verification and unconditionally prefers the client-supplied value, so an unauthenticated remote request (CVSS vector AV:N/AC:L/PR:N/UI:N/S:U) can dictate the address the plugin believes it is talking to. That single attacker-controlled value feeds two distinct sinks: the per-visitor rate limiter for poll voting, which can be reset arbitrarily by rotating the header, and the entry metadata that records who submitted a form, which is written directly into stored submissions. No CWE identifier was assigned in the supplied data; conceptually the root cause class maps to improper verification of a data source (less-trusted source / spoofing of source identity), and the supplied CVSS list confidentiality impact as low while the independent assessment narrows the realistic impact to integrity only, with no confidentiality or availability effect. The CPE record lists the package generically as cpe:2.3:a:unknown:forminator_forms:*:*:*:*:*:*:*:*, with the affected range being all versions before 1.57.2.1.
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:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Remote unauthenticated header spoofing with no user interaction (AV:N/AC:L/PR:N/UI:N); impact is data manipulation of votes and recorded addresses, so I:L with C:N/A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Forminator Forms WordPress plugin before 1.57.2.1 does not verify that a request came from a trusted proxy before preferring client-supplied forwarding headers over the connecting address, and it uses that value both to enforce its per-visitor voting limit and to record who submitted an entry. Unauthenticated visitors can therefore vote without limit on any poll and can choose the address stored against every submission they make.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Forminator Forms
View allAuthenticated code execution in the Forminator Forms WordPress plugin (before 1.57.2.1) lets a user who holds the plugin
An 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
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-85191
GHSA-642x-qxrr-85pr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB