Skip to main content

Gateway for Vantiv EUVDEUVD-2026-104087

| CVE-2026-106014 MEDIUM
Improper Access Control (CWE-284)
2026-10-19 WPScan GHSA-4573-j266-gqm9
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WooCommerce store using plugin
  2. Delivery
    Place order and reach return handler
  3. Exploit
    Forge unauthenticated payment-return notification
  4. Execution
    Order status set to paid
  5. Impact
    Goods released without payment

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 the target site to be running the 'Gateway for Vantiv on WC' WooCommerce plugin (version ≤1.0.1) and to process payments through its hosted-payment return flow; the attacker must be able to reach the plugin's hosted-payment return handler endpoint and submit a request during/after an order. No authentication, no user interaction, and no non-default configuration are needed - the handler accepts return notifications without verifying their authenticity (CWE-284). The practical limiting factors are narrow: the specific plugin must be installed and actively used as the store's payment gateway, which given the product's niche nature sharply constrains the exposed population; there is no impact on sites not using this plugin or not relying on its hosted-payment return handling.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3) describes a remotely reachable, low-complexity, unauthenticated flaw with no user interaction, but the impact is deliberately scoped to integrity-only and rated Low (C:N/I:L/A:N) - there is no system compromise, data disclosure, or availability loss. The real-world consequence is financial/business-logic fraud: an attacker forges a payment-return notification to mark WooCommerce orders as paid without paying. Publicly available exploit code exists (reported by WPScan), which raises practical exploitability, but no EPSS score was provided in the input and the CVE is NOT listed in CISA KEV, so there is no evidence of active, widespread exploitation. This is best treated as a moderate, merchant-specific priority rather than a critical infrastructure threat: the medium severity is driven by trivial exploitability against a payment flow, while the limited scope and the apparently niche affected product cap the aggregate risk. Note the signals are consistent (no conflict between vector and description); the main missing data points are EPSS probability and any vendor/patch advisory confirming a fixed version.

Exploit ScenarioDerived

An attacker places an order in a WooCommerce store running this plugin, then sends a crafted HTTP request to the plugin's hosted-payment return handler mimicking a successful Vantiv payment notification, which the plugin accepts without validating authenticity. The order is marked paid and fulfillment/shipment proceeds even though no payment occurred. Public exploit code for this technique is available via WPScan, lowering the skill required.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

Unauthenticated attackers can mark WooCommerce orders as paid without actually paying in sites running the 'Gateway for Vantiv on WC' WordPress plugin through version 1.0.1. The plugin's hosted-payment return handler accepts return notifications without verifying their authenticity (CWE-284), yielding a low-integrity impact (CVSS 5.3, I:L) with no confidentiality or availability effect. Publicly available exploit code exists, and exploitation is limited to sites that use this specific plugin as their payment gateway and expose the return handler.

RemediationAI

Apply the latest vendor release of the 'Gateway for Vantiv on WC' plugin; the provided intelligence identifies versions through 1.0.1 as affected but does not specify an exact fixed version, so check the WPScan advisory (https://wpscan.com/vulnerability/30ccd424-a0a1-40a9-93ab-5def94eb0073/) and NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-106014) for the current fixed release. If an update is not yet available, disable the plugin and use an alternate payment gateway - the trade-off is loss of Vantiv hosted-payment functionality. Alternatively, restrict access to the plugin's hosted-payment return handler to expected Vantiv source IP ranges at the WAF or reverse-proxy layer and/or add a shared-secret token check; the trade-off is that Vantiv IP ranges can change and overly strict filtering may break legitimate return notifications. Operationally, validate order-paid status against Vantiv settlement records before fulfillment to catch forged notifications, and monitor for orders marked paid without a corresponding Vantiv transaction. Publicly available exploit code exists, so prioritize these controls on any site still running the affected plugin.

Affected VersionsENISA

Gateway for Vantiv on WC 0 ≤1.0.1

Affected Packages

euvd gateway_for_vantiv_on_wc no fix

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

The plugin integrates the Vantiv (Worldpay) hosted payment flow into WooCommerce. In that flow, the customer is redirected to the payment provider and then returned to the merchant site, where the plugin handles a notification/return request to update the order status. CVE-2026-106014 exists because the hosted-payment return handler does not verify that the notification originated from Vantiv - there is no signature, token, or other authenticity check - so a remote unauthenticated attacker who can reach the handler can submit a crafted request that marks an order as paid. CWE-284 (Improper Access Control) captures the missing authorization/verification on the handler. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N indicates network reachability, no privileges or user interaction, and integrity-only impact. CPE data lists the product under an unknown vendor with a wildcard version, and EUVD lists Gateway for Vantiv on WC 0 ≤1.0.1 as affected.

Know when Gateway For Vantiv On Wc 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

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Remote unauthenticated request to the return handler with no user interaction (AV:N/AC:L/PR:N/UI:N); only order-paid state is forged, so I:L with C:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 19, 2026 - 10:23 NVD
5.3 (MEDIUM)
CVE Published
Oct 19, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 19, 2026 - 06:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Gateway for Vantiv on WC WordPress plugin through 1.0.1 does not verify the authenticity of the payment notification received on its hosted-payment return handler, allowing unauthenticated attackers to mark orders as paid without actually paying.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Rare
obscure Vantiv-specific WooCommerce gateway plugin, tiny install base
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy