Security Resilience

CVE-2026-4987

Published
28 March 2026
Modified
24 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.012 67th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-4987 is a high-severity Improper Input Validation (CWE-20) vulnerability in Wordpress (inferred from references). Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-4987 is a Payment Amount Bypass vulnerability affecting the SureForms – Contact Form, Payment Form & Other Custom Form Builder plugin for WordPress in all versions up to and including 2.5.2. The issue stems from the create_payment_intent() function, which performs payment validation based solely on a user-controlled parameter. By setting the form_id parameter to 0, attackers can bypass configured form payment-amount validation. The vulnerability has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) and is associated with CWE-20 (Improper Input Validation). It was published on 2026-03-28.

Unauthenticated attackers can exploit this vulnerability remotely with low complexity and no user interaction required. Exploitation involves manipulating the form_id parameter during payment intent creation, allowing attackers to generate underpriced payment or subscription intents that bypass the intended amount restrictions set by form configurations.

Mitigation is addressed in the plugin's WordPress trac changeset 3488858, which likely includes the patch fixing the validation logic. Additional details and threat intelligence are available from Wordfence at their vulnerability page. Security practitioners should update to a version beyond 2.5.2 and review any existing SureForms payment forms for exposure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The SureForms – Contact Form, Payment Form & Other Custom Form Builder plugin for WordPress is vulnerable to Payment Amount Bypass in all versions up to, and including, 2.5.2. This is due to the create_payment_intent() function performing a payment validation…

more

solely based on the value of a user-controlled parameter. This makes it possible for unauthenticated attackers to bypass configured form payment-amount validation and create underpriced payment/subscription intents by setting form_id to 0.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-23263Shared CWE-20
CVE-2024-31865Shared CWE-20
CVE-2024-25656Shared CWE-20
CVE-2023-4552Shared CWE-20
CVE-2023-0026Shared CWE-20
CVE-2024-12401Shared CWE-20
CVE-2025-21280Shared CWE-20
CVE-2026-64046Shared CWE-20
CVE-2024-45167Shared CWE-20
CVE-2024-31227Shared CWE-20

Affected Assets

Wordpress
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.

References