Security readout for executives and security teams
Plain-English summary
CVE-2026-4987 affects the WordPress SureForms plugin in versions up to and including 2.5.2. An unauthenticated attacker may be able to bypass configured payment amount validation and create payment or subscription intents at an incorrect lower amount.
Executive priority
Prioritize remediation for any revenue-generating WordPress site using SureForms payment or subscription forms. The issue can directly affect transaction integrity without requiring authentication.
Technical view
The issue is described as a payment amount validation bypass in SureForms' create_payment_intent() flow. The validation reportedly relies on a user-controlled form identifier, allowing payment amount checks to be bypassed when handling payment or subscription intent creation. The CVSS 3.1 score is 7.5 with network attack vector, low complexity, no privileges, and no user interaction required, with high integrity impact.
Likely exposure
Public WordPress sites using SureForms – Contact Form, Payment Form & Other Custom Form Builder, especially sites running version 2.5.2 or earlier and using SureForms payment or subscription forms. Sites not using the plugin, not exposing SureForms payment flows, or already updated beyond the affected range are less likely to be exposed.
Exploitation context
The bundle does not indicate CISA KEV listing and does not provide evidence of active exploitation. The risk is still significant because the reported attack path is unauthenticated, remote, low complexity, and affects payment integrity rather than confidentiality or availability.
Researcher notes
The affected-version evidence in the bundle is strongest in the title and description, which state all versions up to and including 2.5.2. The structured affected entry appears sparse and should not be used to narrow exposure without vendor confirmation. No exploit code, payload details, or active exploitation evidence are included in the bundle.
Mitigation direction
- Identify all WordPress sites running the SureForms plugin and confirm the installed version.
- If SureForms is version 2.5.2 or earlier, update to the latest vendor-provided release and verify the fixed version against official vendor or WordPress plugin guidance, since the bundle does not explicitly name a patched version.
- If immediate updating is not possible, temporarily disable SureForms payment and subscription forms or the plugin itself until vendor guidance can be applied.
- Review payment provider records for unexpected underpriced payments or subscriptions created through SureForms forms.
- Ensure payment amount validation is enforced server-side and not based solely on user-controlled request values.
Validation and detection
- Confirm the installed SureForms version on every WordPress instance.
- Verify exposed payment and subscription forms are no longer running a version described as affected, up to and including 2.5.2.
- Review vendor changelog or the referenced WordPress plugin changeset to confirm the payment intent validation behavior was corrected.
- Check recent payment and subscription records for mismatches between configured form amounts and actual payment intent amounts.
- Run an authorized regression test confirming payment amounts are derived from trusted server-side form configuration and cannot be reduced through request manipulation.
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-20: 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 lookupCVE-2026-4987 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.