Security readout for executives and security teams
Plain-English summary
CVE-2026-2888 lets unauthenticated visitors reduce payment amounts on some WordPress sites using Formidable Forms payment features. The risk is financial integrity, not data theft or full site takeover. It matters most for sites selling goods or services through dynamic pricing forms.
Executive priority
Prioritize for ecommerce or service-payment sites using Formidable Forms dynamic pricing. The business risk is direct revenue loss through manipulated payment amounts. Treat as moderate urgency unless the affected payment workflow is business-critical or high-volume.
Technical view
Formidable Forms up to and including 6.28 exposes an authorization bypass in the Stripe payment amount AJAX flow. The frm_strp_amount handler uses a public nonce and attacker-controlled JSON to overwrite $_POST, then recalculates amounts through dynamic field shortcode resolution. Affected exposure is tied to forms using dynamic pricing with field shortcodes.
Likely exposure
Public WordPress sites running Formidable Forms <= 6.28 are potentially exposed if they use payment forms with dynamic pricing based on field shortcodes. Sites not using these payment and pricing features have lower practical exposure based on the provided description.
Exploitation context
The source bundle reports unauthenticated network access and low attack complexity. CISA KEV is false, and no provided source states active exploitation. The practical abuse scenario is underpayment before payment completion, producing revenue loss or order-processing issues.
Researcher notes
This is CWE-639 authorization bypass with integrity impact. The public nonce appears to provide CSRF protection, not user authorization. Source evidence points to update_intent_ajax, generate_false_entry, and Stripe hook code paths. The provided data does not name a specific fixed release.
Mitigation direction
- Check vendor and WordPress plugin guidance for the fixed release.
- Update Formidable Forms from versions up to 6.28 when an update is available.
- Review payment forms using dynamic pricing with field shortcodes.
- Temporarily disable affected dynamic pricing payment flows if update timing is uncertain.
- Reconcile recent orders for mismatches between expected and paid amounts.
Validation and detection
- Inventory WordPress sites using the Formidable Forms plugin.
- Confirm whether installed versions are 6.28 or earlier.
- Identify forms using Stripe payments and dynamic field-shortcode pricing.
- Review payment logs for reduced or inconsistent PaymentIntent amounts.
- Validate fixes in staging using legitimate checkout test cases only.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2888 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b8be3b6e-a035-4e6f-ba2b-ce9e59ebf2e0?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/formidable/tags/6.28/stripe/models/FrmStrpLiteAuth.php#L322CVE reference
- https://plugins.trac.wordpress.org/browser/formidable/tags/6.28/stripe/controllers/FrmStrpLiteHooksController.php#L88CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3480574%40formidable%2Ftrunk&old=3460198%40formidable%2Ftrunk&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.