Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with vulnerable plugin
-
DeliveryInitiate checkout/payment flow as anonymous user
-
ExploitIntercept outbound HTTP payment parameters via proxy
-
ExecutionModify parameters to assert successful payment status
-
PersistSubmit manipulated request to plugin endpoint
-
ImpactPlugin records order as paid without payment gateway confirmation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security Server-side parameter enforcement
|
| Exploitation Conditions | The target WordPress site must have Best Payments Plugin for WP version 4.6.19 or earlier installed and active with at least one publicly accessible payment form or checkout flow. CVSS PR:N confirms exploitation requires no authentication - anonymous visitors who can reach the checkout page are potential attackers. CVSS AC:H limits exploitation to individuals with the technical ability to intercept and modify HTTP requests during an active payment session (requiring a tool such as Burp Suite or a browser developer console) and sufficient knowledge of the plugin's parameter naming and expected values. Exploitation is further constrained by the need to actively engage a payment flow rather than passively scanning endpoints. No non-default WordPress configuration is required beyond having the plugin installed and operational; any site running a vulnerable version with an active storefront is at risk during checkout sessions. The limiting factors for defenders to note are: AC:H eliminates script-kiddie mass exploitation; no public exploit reduces immediate threat surface; and C:N/A:N means the flaw cannot be leveraged for data exfiltration or service disruption. |
| Impact | The CVSS 3.1 score is 5.9 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N. The network attack vector and absence of privilege requirements (PR:N, confirmed by CVSS) lower the bar for any attacker who can reach the checkout flow, but high attack complexity (AC:H) requires deliberate HTTP parameter manipulation and knowledge of the plugin's payment flow - ruling out trivial automated scanning. Integrity impact is high (I:H), meaning successful exploitation allows free acquisition of goods or services on affected stores; confidentiality and availability are entirely unaffected (C:N/A:N). No EPSS data was provided, so exploitation probability cannot be quantified. The vulnerability is not listed in CISA KEV and no public exploit code has been identified, indicating no confirmed active exploitation at time of analysis. Given AC:H and the absence of public exploit tooling, SSVC automatable signal is low; however, motivated actors manually targeting specific high-value merchants represent a plausible threat. The business risk is meaningful for e-commerce operators but unlikely to manifest as mass-exploitation campaigns. No conflicting data signals are present in the available intelligence. |
| Exploit ScenarioDerived | An attacker targeting a WordPress store initiates a legitimate checkout session, then uses an HTTP interception proxy (such as Burp Suite) to capture and modify the payment parameters submitted during the flow - for example, changing a payment status field or amount parameter to indicate a successful transaction before submitting the request. The vulnerable plugin accepts these client-supplied values without re-verifying against a server-side authoritative record or payment gateway callback, records the order as paid, and delivers goods or services without any funds being transferred. No public exploit code is identified at time of analysis, but the attack requires only standard HTTP interception skills and familiarity with the plugin's parameter structure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 15, 2026
Payment bypass in Best Payments Plugin for WP (versions ≤ 4.6.19) allows unauthenticated remote attackers to circumvent payment verification by manipulating HTTP parameters the plugin incorrectly treats as immutable, enabling completion of purchases without actual payment. Rooted in CWE-472 (External Control of Assumed-Immutable Web Parameter), the flaw directly threatens the financial integrity of any WordPress e-commerce site relying on this plugin for order processing. No public exploit is identified and CVSS AC:H indicates exploitation requires deliberate parameter manipulation during an active payment flow, limiting mass-exploitation risk despite the unauthenticated attack vector.
RemediationAI
No vendor-released patch version is independently confirmed from available data; administrators should immediately consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-payment-form/vulnerability/wordpress-best-payments-plugin-for-wp-plugin-4-6-19-payment-bypass-vulnerability?_s_id=cve for the latest fix status and upgrade instructions. If a patched version has been released in the WordPress plugin repository, updating to it is the primary remediation. As a compensating control where patching is not immediately possible, temporarily deactivating the plugin eliminates exposure entirely but halts payment processing. Restricting checkout page access to authenticated users only, if the plugin supports such configuration, raises the exploitation bar from PR:N to at least PR:L. Deploying a WAF rule to flag or block anomalous parameter values in payment-related POST requests (e.g., unexpected payment status values not originating from the payment gateway callback endpoint) provides partial mitigation with minimal trade-offs. Server-side re-validation of all payment-state data against authoritative payment gateway records - rather than client-submitted fields - should be treated as a permanent architectural requirement for any replacement or updated plugin version.
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
CWE-472 (External Control of Assumed-Immutable Web Parameter) describes a class of flaw where an application transmits state data to the client - such as hidden form fields, cookies, or query parameters encoding payment status, order amount, or verification tokens - and later trusts that data as authoritative when it is returned without cryptographic validation or server-side re-verification. The Best Payments Plugin for WP by wpmanageninja (CPE: cpe:2.3:a:wpmanageninja:best_payments_plugin_for_wp:*:*:*:*:*:*:*:*) processes payments in WordPress environments and, based on the CWE and CVSS vector, appears to pass payment-state parameters client-side without signing or binding them to a server-authoritative record. When these parameters are submitted back by the client, the plugin accepts them at face value, treating a client-supplied 'payment successful' signal as legitimate. The CVSS AC:H metric confirms that successful exploitation requires understanding the plugin's specific parameter structure and the sequence of the payment flow, distinguishing this from a trivially automatable flaw.
Know when Best Payments Plugin For Wp 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:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Network-reachable unauthenticated flaw with AC:H for required parameter manipulation knowledge; I:H for payment bypass; C and A remain N as only financial integrity is impacted.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated Bypass Vulnerability in Best Payments Plugin for WP <= 4.6.19 versions.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-36820
GHSA-g7qv-r436-2gvc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB