Skip to main content

AmazonPay Plugin CVE-2026-103671

| EUVDEUVD-2026-100939 MEDIUM
External Control of Assumed-Immutable Web Parameter (CWE-472)
2026-10-14 jpcert GHSA-9xxh-8f25-hpwm
5.3
CVSS 4.0 · Vendor: jpcert
View

Attack ChainAIDerived

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

  1. Access
    Craft malicious order parameter/link
  2. Exploit
    Lure shopper into checkout flow
  3. Execution
    Trigger redirect to attacker site
  4. Impact
    Harvest submitted account information

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

Exploitation requires an EC-CUBE 4-series store with the AmazonPay plugin installed and active (AmazonPay v2 plugin for the 4.0/4.1, 4.2/4.3, and 4.2/4.3 bundle editions, or the AmazonPay v1 plugin for the 4.0 series), AND a victim shopper actively engaged in the ordering/checkout process. The attacker supplies an externally controlled, assumed-immutable web parameter that the checkout flow trusts, causing redirection to an arbitrary external site where account information can be captured. Limiting factors: the attack is not self-contained - it needs victim interaction during an in-progress order (UI:R), so a user must be socially engineered into following the tampered flow; there is no direct server-side confidentiality or availability impact and the attacker gains no privileges on the shop itself. Stores without the AmazonPay plugin are unaffected.

Impact

This is a moderate-severity (CVSS 4.7) open-redirect-style flaw (CWE-472, external control of an assumed-immutable web parameter) in the AmazonPay plugin for the EC-CUBE 4 e-commerce platform. The CVSS 3.0 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N) indicates a network-reachable, low-complexity issue requiring no attacker authentication (PR:N) but mandatory victim interaction (UI:R) during the checkout flow, with a scope change (S:C) reflecting that harvested account information crosses from the shop to an attacker-controlled destination. The direct technical impact is limited (integrity-low only; no confidentiality or availability impact on the host itself), so this is NOT a system-compromise bug - it is a user-targeted phishing/redirection vector. No EPSS score, CISA KEV listing, or public POC is present in the provided intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the dependence on user interaction and the socially-engineered nature of the attack make opportunistic mass-exploitation unlikely. Net assessment: a real but contained risk that merits patching on affected EC-CUBE shops, not an emergency - a medium-CVSS issue whose real-world danger hinges on successful social engineering of shoppers mid-order rather than on an unauthenticated remote takeover.

Exploit ScenarioDerived

An attacker crafts a malicious link or tampered order parameter for an EC-CUBE 4 storefront running the AmazonPay plugin and lures a shopper to begin or continue checkout. Because the ordering flow trusts an attacker-controllable parameter, the victim is redirected mid-order to an attacker-controlled site that mimics the payment/login step and harvests their account information. No public exploit code is identified at time of analysis, and success depends on the victim following the crafted ordering flow (UI:R).

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Checkout-flow open redirection in the AmazonPay plugin for EC-CUBE 4 allows remote, unauthenticated attackers to send shoppers to an arbitrary external website during the ordering process, where the shopper's account information can be captured. Affected deployments are EC-CUBE 4-series stores running the AmazonPay v2 plugin (4.0/4.1 series, 4.2/4.3 series, and the 4.2/4.3 bundle edition) or the v1 plugin for the 4.0 series; stores without the plugin are unaffected. Rated CVSS 4.7 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N), there is no public exploit identified at time of analysis, and exploitation is not self-contained: it requires a victim shopper to be actively engaged in the order/checkout process and socially engineered into following the tampered flow, which limits both reach and reliability.

RemediationAI

Apply the updated AmazonPay plugin release published for the corresponding EC-CUBE 4 plugin line, and confirm the exact fixed version in the vendor advisories at https://www.ec-cube.net/news/detail.php?news_id=490 and https://jvn.jp/en/jp/JVN43511918/ rather than relying on the wildcard CPE ranges given here; plugin updates on EC-CUBE are applied through the store owner's plugin management and should be verified on a staging store before rollout. Where an update cannot be deployed immediately, the most effective compensating control is to disable the AmazonPay plugin entirely - the trade-off is that Amazon Pay disappears as a checkout payment option, which will affect conversion but removes the vulnerable ordering path. As a secondary, code-level mitigation for shops able to customize the plugin, enforce a server-side allowlist of permitted redirect destinations (shop domain and Amazon Pay endpoints only) instead of trusting the client-supplied return parameter, and reject or normalize any unexpected external URLs; this requires maintaining the plugin fork through future upgrades, which adds operational overhead. On the user side, shop operators should warn customers that legitimate EC-CUBE/Amazon Pay checkout never redirects to third-party login pages mid-order, and shoppers should navigate to Amazon Pay via the shop itself rather than following links received out-of-band. Note that no public exploit code has been identified at the time of analysis, so there is no evidence of active exploitation and the timing of the patch is not driven by an observed campaign.

Affected VersionsENISA

AmazonPay V2 Plugin (4.0/4.1 series) v1.1.7 ≤v1.1.12
AmazonPay V2 Plugin (4.2/4.3 series) v4.2.3 ≤v4.3.1
AmazonPay V2 Plugin (4.2/4.3 series, Bundle Edition) v4.3.1
AmazonPay V2 Plugin (4.2/4.3 series) v4.2.0 ≤v4.2.2
AmazonPay V2 Plugin (4.0/4.1 series) v1.0.0 ≤v1.1.6
AmazonPay Plugin (4.0 series) 0 ≤v1.3.0

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is an instance of CWE-472 (External Control of Assumed-Immutable Web Parameter): the plugin's ordering flow trusts a web parameter that the application assumes cannot be modified by the user, but which is in fact attacker-controllable, so the trusted value is used to build a redirect destination. Because that value is echoed into the navigation decision rather than validated server-side against an allowlist, the shopper's browser is sent to an arbitrary external site that can mimic the shop or Amazon Pay branding and harvest credentials or order data. The vulnerability sits inside the AmazonPay payment plugin, not in the EC-CUBE core, so the blast radius is confined to EC-CUBE 4-series installs with the plugin active (per the provided CPEs: amazonpay_v2_plugin 4.0/4.1 series, 4.2/4.3 series, 4.2/4.3 series bundle edition, and amazonpay_plugin 4.0 series). The CVSS vector's S:C reflects that the manipulated redirect takes effect outside the vulnerable component (on an attacker-controlled site), while C:N/I:L/A:N against the shop itself means the attacker gains no privileges and causes no server-side data exposure or denial of service - the harm is to the redirected shopper. PR:N combined with UI:R means the attacker needs no authentication on the shop but does need a live, in-progress order and victim interaction, which explains the modest 4.7 score despite the network-reachable attack path.

Know when Amazonpay V2 Plugin 4 0 4 1 Series 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 (jpcert) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
vuln.today AI 4.7 MEDIUM

Network-reachable with no attacker auth (PR:N) but the victim must act mid-checkout (UI:R); the redirect sends data to another origin (S:C) with only limited integrity impact and no C/A on the host.

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

Primary rating from Vendor (jpcert).

CVSS VectorVendor: jpcert

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
Low
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Oct 14, 2026 - 09:22 NVD
4.7 (MEDIUM) 5.3 (MEDIUM)

DescriptionCVE.org

External control of assumed-Immutable web parameter issue exists in EC-CUBE plugin (for EC-CUBE 4 series) "AmazonPay Plugin". If exploited, the user may be redirected to an arbitrary website during the ordering process. As a result, user's account information may be obtained.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Low
Japan-centric EC-CUBE payment plugin; limited global enterprise footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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 No
EPSS 0.2%
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
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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