Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach plugin payment-verification endpoint
-
DeliverySend unauthenticated verification requests
-
ExploitRecord rate-limit timestamps as attacker
-
ExecutionExhaust 24-hour daily allowance
-
ImpactLegitimate verifications refused
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the target WordPress site to run Formidable Forms 6.5-6.x with a payment gateway configured such that the plugin's rate-limited payment-verification feature is active - sites not processing payments through Formidable Forms are not affected. Given the condition is met, no further prerequisites apply: the verification endpoint records the rate-limit timestamp without authenticating the caller (AV:N/AC:L/PR:N/UI:N), so any remote unauthenticated attacker can trigger it against default configurations. The principal limiting factor is therefore deployment-specific (payment processing must be enabled), not an authentication or user-interaction barrier; impact is further limited to a 24-hour denial of the verification function rather than full site outage. |
| Impact | This is a genuine but bounded availability issue, not a critical system-compromise flaw. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) correctly reflects remote, unauthenticated, low-complexity exploitation with no user interaction, but the A:H rating overstates impact: the defect (CWE-400, uncontrolled resource consumption) only disables payment-gateway verification for 24 hours, not the whole site, so a partial-availability (A:L) view is more honest. Confidence/integrity are untouched (C:N/I:N). Exploitation status is 'publicly available exploit code exists' - a POC is published by WPScan, but there is no CISA KEV listing and no EPSS score in the input, so there is NO evidence of active or widespread exploitation; POC availability must not be conflated with in-the-wild use. No SSVC data was provided. Net: prioritize for sites that actually process payments through Formidable Forms, but treat it below any flaw affecting confidentiality or integrity. EPSS is absent, so probabilistic exploitation likelihood cannot be stated. |
| Exploit ScenarioDerived | An attacker with no account and no user interaction sends repeated unauthenticated requests to the Formidable Forms payment-gateway verification endpoint, which records rate-limit timestamps without verifying the caller's identity. By exhausting the daily verification allowance, the attacker causes all legitimate payment-verification attempts to be refused for the next 24 hours. A public POC exists (WPScan), and the low attack complexity (AC:L) means the abuse requires only crafted HTTP requests. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Unauthenticated remote attackers can exhaust the daily rate-limit allowance for payment gateway verification in the Formidable Forms WordPress plugin on sites running versions 6.5 through 6.x with a payment gateway configured, causing legitimate verification attempts to be refused for up to 24 hours. The plugin records the rate-limit timestamp without verifying the caller's identity, so the issue is a bounded availability impact against the verification function rather than a full site outage or system compromise. Publicly available exploit code exists, a vendor patch is available in version 7.0, and the independently assessed impact is availability-only.
RemediationAI
Upgrade the Formidable Forms WordPress plugin to version 7.0 or later, the vendor-released fix for versions before 7.0. If immediate upgrade is not possible, disable Formidable Forms payment processing or the payment gateway verification feature until patched; this removes the attack surface but stops legitimate payment verification. As a compensating control, restrict access to the plugin's payment-verification endpoint to known payment-processor IP ranges via web server or WAF rules, accepting the trade-off that processor IP changes can break legitimate callbacks, and monitor for repeated unauthenticated verification requests. Vendor advisory: https://wpscan.com/vulnerability/6bdc69fa-7db1-4790-9147-30ebd03580b0/.
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
Formidable Forms is a WordPress plugin that can process payments through configured gateways and uses a daily rate-limit timestamp to control payment gateway verification requests. The root cause is an uncontrolled resource consumption weakness (CWE-400): the plugin does not verify the identity of the caller before recording the timestamp used for rate limiting, so an unauthenticated remote request can consume the finite daily allowance. The affected CPE is cpe:2.3:a:unknown:formidable_forms:*:*:*:*:*:*:*:* with EUVD listing Formidable Forms 6.5 <7.0; the CPE vendor field is unknown, but the affected product is Formidable Forms. Exploitation requires the WordPress site to run Formidable Forms 6.5-6.x with a payment gateway configured and the plugin's rate-limited payment-verification feature active; sites not processing payments through Formidable Forms are not affected.
Know when Formidable 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:N/I:N/A:H
Remote unauthenticated and low-complexity (AV:N/AC:L/PR:N/UI:N) matches the input, but availability loss is partial - only payment verification is denied for 24h - so A:L rather than A:H, with C:N/I:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Formidable Forms WordPress plugin before 7.0 does not verify the identity of the caller before recording the timestamp it uses to rate limit payment gateway verification requests, allowing unauthenticated attackers to consume the daily allowance and cause legitimate verification attempts to be refused for the next 24 hours.
Technical POC Analysis
CWE-400 (Uncontrolled Resource Consumption) - specifically, exhaustion of a bounded, per-day rate-limit allowance rather than memory or CPU.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Formidable Forms versions 6.5 through 6.x with a configured payment gateway can have their daily verification rate limit exhausted by remote requests, causing legitimate payment verifications to be refused for up to 24 hours. This is a bounded availability issue affecting payment confirmation workflows on affected WordPress sites, not a site compromise or data breach. Publicly available exploit code exists, so leadership should prioritize patching because repeated verification refusals could disrupt revenue and customer trust even though the blast radius is limited.
Apply vendor patch (Formidable Forms 7.0); until upgraded, monitor payment gateway verification failures and consider temporary rate-limit or fallback verification adjustments.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Formidable Forms
View allThe Formidable Forms WordPress plugin before 6.3.1 does not adequately authorize the user or validate the plugin URL in
Unauthenticated visitors can inject arbitrary WordPress shortcodes, including attacker-chosen attributes, into Formidabl
The Formidable Forms WordPress plugin before 6.14.1 does not sanitise and escape some of its settings, which could allow
Stored HTML injection in the WordPress Formidable Forms plugin before 6.35 allows unauthenticated visitors to submit for
The Formidable Forms - Contact Form, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for WordPress i
The Formidable Forms - Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for Word
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Strategy11 Form Builder T
The Formidable Forms - Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder plugin for Word
Missing Authorization vulnerability in Strategy11 Team Formidable Forms formidable allows Exploiting Incorrectly Configu
EUVD-2026-107084
GHSA-4w7f-p9m2-jxgx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB