Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify store running vulnerable Mintpay plugin
-
DeliveryCraft forged payment callback request
-
ExploitSubmit unauthenticated callback to plugin endpoint
-
ExecutionPlugin processes without authenticity check
-
ImpactMark order paid / cancel orders / read customer data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only that the Mintpay for WooCommerce plugin (version ≤ 2.2.3) be installed and active on a reachable WooCommerce store; per the description the plugin does not verify the authenticity of the payment callback it processes, so a remote, unauthenticated attacker can invoke that callback handler directly. Consistent with AV:N/AC:L/PR:N/UI:N, there is no authentication, user interaction, or special non-default configuration requirement stated in the sources. The practical limiting factors are narrow: the target store must run this specific regional BNPL plugin, and an attacker targeting a particular transaction may need to reference or enumerate valid order identifiers, though the advisory describes action against arbitrary orders. |
| Impact | This is a moderate-severity access-control flaw (CWE-284) in a specific WooCommerce payment-gateway plugin, and the signals are internally consistent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates a remotely reachable, low-complexity, unauthenticated issue requiring no user interaction, which matches the description of a forgeable, unauthenticated payment callback. Impact is bounded: C:L/I:L/A:N reflects limited disclosure of order/customer data and limited integrity impact (marking orders paid, cancelling orders) without system-level compromise, so the 6.5 (Medium) score is credible and not inflated. There is no CISA KEV listing and no EPSS score in the input, so widespread or automated exploitation is not demonstrated; the only exploitation signal is a single WPScan PoC reference that is not verified as working exploit code. The vuln.today decision label is 'this_month' (not act_now/emergency), consistent with a real but non-emergency priority. The main real-world driver of risk is financial: an attacker able to mark orders 'paid' without payment could defraud a merchant, which may matter more to affected store owners than the Medium CVSS implies - but this is scoped to stores actually running this plugin. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a forged Mintpay payment-callback request to a WooCommerce store running the vulnerable plugin; because the plugin never verifies the callback's authenticity, the attacker can mark an order as paid without any real payment, cancel other customers' orders, or read back order details including customer contact information. A public PoC reference (WPScan) exists but is not verified as working exploit code, so exploitation is plausible but not demonstrated at scale. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Unauthenticated remote attackers can mark or cancel arbitrary WooCommerce orders and disclose customer contact details on stores running Mintpay for WooCommerce through version 2.2.3, because the plugin processes payment callbacks without verifying their authenticity. The issue is rated CVSS 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) and tracked as CWE-284; it is not reported as actively exploited, and the available PoC reference is not verified as working exploit code. Vuln.today prioritizes remediation this month.
RemediationAI
No vendor-released patch version is identified in the provided data; treat version 2.2.3 and earlier as affected and check the WPScan advisory at https://wpscan.com/vulnerability/593fa052-8917-416c-944b-11b890c9ab50/ for an updated release. If Mintpay checkout is not essential, deactivate and remove the plugin, which eliminates the callback endpoint but removes Mintpay BNPL payments from checkout. If the plugin must remain active, restrict the callback route with a WAF or reverse-proxy rule to accept only requests from Mintpay's published egress ranges and reject others, accepting that legitimate callbacks break if Mintpay changes its infrastructure; also reconcile WooCommerce order status against Mintpay settlement records and review orders for unauthorized paid or cancelled transitions. Upgrade to a vendor-fixed version as soon as one is published.
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
Mintpay for WooCommerce is a WordPress payment-gateway integration that relies on a callback endpoint to receive payment-status notifications from the Mintpay service and update WooCommerce order state. The flaw is an access-control failure (CWE-284): the callback handler does not validate a shared secret, signature, or other proof that the request came from Mintpay, so the endpoint's order-state-changing actions are reachable by unauthenticated remote users. With AV:N/AC:L/PR:N/UI:N, no authentication or user interaction is required; the main prerequisites are an active installation of the plugin at version 2.2.3 or earlier on a reachable WooCommerce store and, for targeted actions, knowledge of valid order identifiers. The CPE record uses an unknown vendor and a wildcard version, so affected package identity is confirmed by the plugin name and EUVD's ≤2.2.3 range rather than by a precise vendor CPE.
Know when Mintpay For Woocommerce 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:L/I:L/A:N
Unauthenticated remote callback with no interaction gives AV:N/AC:L/PR:N/UI:N; limited order-data disclosure (C:L) and order-state tampering (I:L) with no availability impact (A:N).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Mintpay for WooCommerce WordPress plugin through 2.2.3 does not verify the authenticity of the payment callback it processes, allowing unauthenticated attackers to mark arbitrary orders as paid, to cancel arbitrary orders, and to disclose order details including customer contact information.
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-109620
GHSA-qwjc-72ww-h64x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB