Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged authenticated account
-
DeliveryIdentify Administrator user ID
-
ExploitCall wpcsa_login with admin ID
-
ExecutionReceive full Administrator session cookie
-
ImpactTake over admin session, full site control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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 | Exploitation requires an authenticated account on the target WordPress/WooCommerce site (PR:L) and that the WPC Shop as a Customer for WooCommerce plugin (version <=2.0.0) is installed and active. The attacker must reach the wpcsa_login endpoint and supply the target Administrator's user ID (WordPress user IDs are low, enumerable, and often guessable - e.g., ID 1). No password, nonce bypass, user interaction, or non-default configuration is otherwise needed; the defect is in the endpoint's missing role validation itself. The limiting factor is solely the need for any authenticated session, which is low-friction given the plugin's customer-impersonation purpose. |
| Impact | This is a genuine high-priority vulnerability, not a high-CVSS-but-low-real-risk case. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8) is well-justified: an authenticated low-privileged user can escalate to full Administrator with network access and low complexity, yielding complete confidentiality, integrity, and availability impact. The flaw is a logic/authorization defect (CWE-269) - the wpcsa_login endpoint issues an Administrator session cookie without password or role validation - so exploitation is deterministic and reliable once the attacker has any authenticated foothold, which strongly favors real-world abuse. Countervailing signals lowering urgency: no EPSS score was provided, the CVE is NOT in CISA KEV, and no public exploit code is referenced, so there is no confirmation of active exploitation. The one true gating factor is PR:L - the attacker must first obtain an authenticated account; however, the plugin's 'shop as a customer' impersonation purpose means low-privileged accounts (e.g., shop managers or any registered customer, depending on configuration) are exactly the intended user base, making the prerequisite easy to meet on many stores. Net: a reliable, trivially-weaponizable account-takeover primitive with no exploitation observed yet - patch promptly where the plugin is installed. |
| Exploit ScenarioDerived | An attacker registers or already holds a low-privileged authenticated account on a WooCommerce store running the vulnerable plugin. They send a request to the wpcsa_login endpoint supplying a known Administrator's user ID (e.g., ID 1) instead of a customer ID; the plugin fails to check the target role and returns a valid Administrator session cookie with no password required. No public proof-of-concept is referenced, but the attack is network-based, low-complexity, and fully scriptable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Authenticated privilege escalation in WPC Shop as a Customer for WooCommerce (versions up to and including 2.0.0) enables any logged-in user to take over an Administrator account by supplying the Administrator's user ID to the wpcsa_login endpoint, receiving a full Administrator session cookie without the Administrator's password. The flaw stems from missing role validation (CWE-269) before issuing a session, and WordPress user IDs are trivially enumerable. No public exploit code is identified at time of analysis, but the vendor-released patch 2.0.1 is available and this is assessed as a genuine high-priority vulnerability.
RemediationAI
Upgrade the WPC Shop as a Customer for WooCommerce plugin to version 2.0.1 or later, which addresses the missing role validation (vendor changeset: https://plugins.trac.wordpress.org/changeset?reponame=&new=3708414%40wpc-shop-as-customer%2Ftags%2F2.0.1&old=3708360%40wpc-shop-as-customer%2Ftags%2F2.0.0). If immediate patching is not possible, deactivate the plugin until the update can be applied; this removes the vulnerable endpoint but disables the customer impersonation feature. As an additional mitigation, reset WordPress authentication salts in wp-config.php to invalidate any existing sessions, and audit Administrator accounts and recent login activity for signs of unauthorized access. Restricting access to the wpcsa_login endpoint (e.g., via a web application firewall) is less reliable because the endpoint is part of the normal plugin functionality and legitimate users may need it; deactivation remains the safest compensating control. The Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/539cdee3-78bc-42a2-9c34-0f7d46f95d16?source=cve should be consulted for any additional guidance.
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
The vulnerability resides in the wpcsa_login endpoint of the WPC Shop as a Customer for WooCommerce plugin, which is designed to let shop managers impersonate customers for support purposes. Code referenced in the plugin's 1.3.6 tag (lines 96, 228, and 253 of wpc-shop-as-customer.php) fails to verify the role of the user identified by the supplied user ID before calling session-issuance logic such as wp_set_auth_cookie. This is an instance of CWE-269 (Improper Privilege Management). Because WordPress assigns sequential user IDs starting at 1 (typically the site Administrator), an authenticated attacker with any role-such as subscriber or customer-can request a session for user ID 1. The endpoint does not require a nonce, password, or any other validation, so the server returns a valid Administrator session cookie. The CVSS v3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (base 8.8), reflecting the remote, low-privilege, no-interaction nature and high confidentiality, integrity, and availability impact of full admin takeover. The CPE string cpe:2.3:a:wpclever:wpc_shop_as_a_customer_for_woocommerce:*:*:*:*:*:*:*:* confirms all versions are affected unless patched.
Know when Wpc Shop As A Customer 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:L/UI:N/S:U/C:H/I:H/A:H
Authenticated low-priv account needed (PR:L) over the network (AV:N) with no user interaction; missing role check yields deterministic full-admin takeover, so C/I/A all High.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The WPC Shop as a Customer for WooCommerce plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 2.0.0 This is due to the plugin not properly validating the target user's role prior to issuing a new authentication session, allowing an authenticated attacker to log in as any WordPress Administrator by directly supplying an Administrator's user ID to the wpcsa_login endpoint and receiving a full Administrator session cookie without supplying the Administrator's password. This makes it possible for authenticated attackers to perform a direct session takeover, gaining full Administrator-level access to the site.
Executive ViewAI
The WPC Shop as a Customer for WooCommerce plugin (versions up to 2.0.0) contains a privilege escalation flaw that allows any logged-in user to gain full Administrator access, potentially leading to complete site takeover, data theft, or malware injection. Organizations running this plugin on their WordPress/WooCommerce sites are at risk, and leadership should prioritize remediation because a single malicious customer account could compromise the entire e-commerce platform and expose sensitive customer data. While no public exploit identified at time of analysis, a vendor-released patch (version 2.0.1) is available.
Apply vendor patch.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-90568
GHSA-wcrr-q656-8gwf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB