Skip to main content

ECPay Ecommerce CVE-2026-32578

| EUVDEUVD-2026-93239 HIGH
Missing Authorization (CWE-862)
2026-10-06 Patchstack GHSA-vvch-jxc2-mq7m
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Register low-privilege subscriber account
  2. Delivery
    Authenticate to WordPress site
  3. Exploit
    Invoke plugin action lacking authorization check
  4. Execution
    Perform unauthorized operation
  5. Impact
    Integrity/availability impact on store

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated low-privilege WordPress account at Subscriber level (CVSS PR:L) on a site running ECPay Ecommerce for WooCommerce version 1.1.2606090 or earlier. Practical exploitability is greatly increased on stores that permit open customer/subscriber self-registration (the default for most WooCommerce shops), which lets an attacker obtain the needed account at will; sites that disable public registration substantially limit exposure. No user interaction (UI:N) and no non-default feature toggle are indicated in the description. Limiting factors: a valid subscriber session is mandatory, confidentiality is unaffected (C:N), and the specific privileged action abused is not detailed in the available data.

Impact

This is a moderate-severity, authenticated access-control flaw (CWE-862, Missing Authorization) rather than a high-priority emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H = 7.1) indicates a network-reachable, low-complexity attack requiring low-level privileges (PR:L - consistent with the 'Subscriber' role named in the title), with no confidentiality impact, limited integrity impact, and high availability impact. The PR:L requirement is the single most important risk-limiting factor: an attacker must already hold a valid low-privilege (subscriber) account on the target WordPress site, so this is not a pre-auth mass-exploitation bug. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so there is no public exploit identified at time of analysis - this contrasts sharply with the 7.1 CVSS and argues against treating it as an immediate, widely-exploited threat. The A:H (high availability) rating is somewhat unusual for a broken-access-control/missing-authorization issue and is not substantiated by the one-line description; this should be verified with Patchstack/the vendor, as the availability impact may be overstated. Overall: patch in normal cycle, with elevated urgency only on sites that allow open subscriber/customer registration (common for WooCommerce stores).

Exploit ScenarioDerived

An attacker registers a free subscriber/customer account on a WooCommerce store running ECPay Ecommerce for WooCommerce <= 1.1.2606090 - trivial where open registration is enabled. Using that authenticated session, they invoke a plugin endpoint or action that fails to check the caller's authorization (CWE-862), performing an operation intended for higher-privileged users. No public exploit code was identified at time of analysis, and low attack complexity (AC:L) means no special timing or conditions are needed once a subscriber account is held.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 06, 2026

Authenticated Subscriber-level attackers can exploit missing authorization checks in ECPay Ecommerce for WooCommerce versions up to 1.1.2606090 to perform actions that may alter store integrity or cause a high availability impact. The flaw requires only a low-privileged account, which is readily available on sites with open registration, but confidentiality is not affected. No public exploit code has been identified, and the vulnerability is not known to be actively exploited.

RemediationAI

No vendor-released patch has been identified at time of analysis. As a workaround, consider temporarily disabling the ECPay Ecommerce for WooCommerce plugin if it is not essential, or restrict subscriber-level accounts by disabling open registration and ensuring only trusted users can register. Monitor the Patchstack advisory and the vendor's website for a patched version, and update promptly once available. Applying least-privilege principles to WordPress roles and auditing subscriber permissions may reduce exposure. Note that disabling the plugin will remove its payment processing functionality, which may impact store operations.

Affected VersionsENISA

ECPay Ecommerce for WooCommerce n/a ≤1.1.2606090

Affected Packages

euvd ecpay_ecommerce_for_woocommerce 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 vulnerability is a missing authorization (CWE-862) issue in the WordPress plugin ECPay Ecommerce for WooCommerce, which integrates ECPay payment services into WooCommerce stores. The plugin fails to verify that a user has the necessary capabilities before executing certain functions, allowing a Subscriber-level user to invoke privileged actions. With a CVSS vector of AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, the flaw is network-exploitable with low complexity, requires authentication, and can result in low integrity impact and high availability impact, potentially allowing an attacker to disrupt store operations or modify limited data. The CPE cpe:2.3:a:techsupport:ecpay_ecommerce_for_woocommerce:*:*:*:*:*:*:*:* indicates all versions up to the fixed release are affected.

Know when Ecpay Ecommerce 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

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
vuln.today AI 7.1 HIGH

Subscriber account needed so PR:L; network-reachable WP endpoint with no interaction gives AV:N/AC:L/UI:N; impacts retained from source, though A:H is weakly supported.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Subscriber Broken Access Control in ECPay Ecommerce for WooCommerce <= 1.1.2606090 versions.

Executive ViewAI

Why It Matters

ECPay Ecommerce for WooCommerce, used by online stores to process payments, contains a high-severity authorization flaw in versions up to 1.1.2606090 that could allow low-privileged users to alter store data or cause service disruptions. This vulnerability poses a risk to e-commerce operations, potentially impacting revenue and customer trust. Given the absence of a vendor patch, leadership should prioritize immediate mitigation efforts to protect store integrity and availability.

Business Impact: High
Compensating Controls

Restrict access to the vulnerable plugin functionality to trusted users, disable open registration if not required, monitor logs for unauthorized changes, and deploy a web application firewall (WAF) with virtual patching rules if available.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Low
Niche ECPay payment-gateway WooCommerce plugin, primarily Taiwan market
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 HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
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