Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister WordPress subscriber account on target site
-
DeliveryAuthenticate and obtain session credentials
-
ExploitSend crafted HTTP request to vulnerable eShipper plugin endpoint
-
ExecutionInject malicious SQL payload into unsanitized parameter
-
PersistQuery traverses database scope boundary
-
ImpactExfiltrate customer PII, order data, and hashed credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid WordPress subscriber-level account on the target site, as confirmed by the PR:L metric in the CVSS vector. The subscriber role is the default role assigned to any registered WordPress user, so any site that permits open user registration is exploitable by self-registered attackers without any prior relationship to the site. Sites that have disabled new user registration and restrict account creation to administrators materially reduce exposure, forcing attackers to first compromise an existing account through other means. No specific non-default plugin feature, configuration setting, or deployment mode is cited as a prerequisite - the vulnerability appears to reside in core plugin functionality accessible to all authenticated subscribers. Limiting factors: attacker must be authenticated at subscriber level or above; exploitation is bounded to the database server accessible to the WordPress installation. |
| Impact | The CVSS 8.5 High score reflects a genuinely significant attack surface: network-reachable, low-complexity SQL injection with scope change and high confidentiality impact. The primary real-world risk limiter is PR:L - attackers must hold a WordPress subscriber account on the target site, which meaningfully reduces opportunistic mass exploitation relative to a PR:N vector. Sites permitting open user registration are effectively exposed to unauthenticated registration followed by immediate exploitation, while sites with registration disabled require a compromised or insider account. No EPSS probability score was provided in the input data, preventing quantitative likelihood calibration. The absence of a KEV listing and no reported POC suggests exploitation has not yet been broadly commoditized, but the low attack complexity (AC:L) means the barrier to independent development is low. The I:N integrity metric in the provided vector warrants scrutiny - SQL injection vulnerabilities typically afford at minimum limited write capability; if the vulnerable endpoint is strictly read-only (e.g., SELECT-only context), I:N is defensible, but this should be verified against the plugin source or vendor advisory. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a target WordPress site running eShipper Commerce 2.16.13 or earlier - possible on any site with open user registration enabled - then sends a crafted HTTP request to the vulnerable plugin endpoint embedding SQL injection payloads. The malicious query traverses the database scope boundary, extracting contents of the wp_users table including hashed passwords and email addresses, which the attacker subsequently uses for credential cracking or account takeover. No public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) means the technique is reproducible by any moderately skilled attacker familiar with WordPress plugin SQL injection patterns. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
SQL injection in the eShipper Commerce WordPress plugin (versions 2.16.13 and earlier) allows subscriber-level authenticated attackers to issue malicious queries against the underlying WordPress database, with scope extending beyond the plugin's own tables due to the CVSS scope-changed flag (S:C), exposing high-confidentiality data such as customer PII, order records, and potentially hashed credentials. The 'Subscriber' designation in the CVE title maps to the lowest default WordPress user role, meaning any registered site user is a viable attacker without elevated privileges. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
RemediationAI
Consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/eshipper-commerce/vulnerability/wordpress-eshipper-commerce-plugin-2-16-13-sql-injection-vulnerability for the confirmed fixed version; no specific patched release number is independently verifiable from the available input data, so the advisory is the authoritative source for patch availability. If a patched release cannot be deployed immediately, the highest-priority compensating control is to disable open WordPress user registration, which prevents unauthenticated actors from self-provisioning subscriber accounts - note this will prevent new user sign-ups and may impact business workflows requiring registration. As a secondary measure, apply WAF rules targeting common SQL injection patterns on eShipper plugin endpoint paths; be aware these rules may generate false positives and should be tested against legitimate plugin traffic before enforcing in blocking mode. Restricting the WordPress installation to trusted IP ranges at the network perimeter can further reduce exposure but is only viable for internal or partner-facing deployments.
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 root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), indicating that user-controlled input is concatenated into SQL queries without proper parameterization or escaping within the plugin. The affected component is the eShipper Commerce WordPress plugin (CPE: cpe:2.3:a:wordpress.com:eshipper_commerce:*:*:*:*:*:*:*:*), a WooCommerce integration for the eShipper carrier and logistics platform. The 'Subscriber' label in the title designates the WordPress subscriber role - the lowest default authenticated role assigned to any registered user - meaning no administrative or editor-level access is required to trigger the injection. The CVSS S:C (scope changed) metric indicates that the injected SQL query can reach data outside the plugin's authorization boundary, likely traversing to core WordPress tables such as wp_users, wp_orders, or other plugin tables sharing the same database.
Know when Eshipper Commerce 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:C/C:H/I:N/A:L
SQL injection canonically affords at least limited write capability; I:L rather than I:N better reflects realistic SQLi impact absent vendor confirmation of a read-only query context.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber SQL Injection in eShipper Commerce <= 2.16.13 versions.
Executive ViewAI
The eShipper Commerce WordPress plugin (versions 2.16.13 and earlier) contains a SQL injection vulnerability allowing any registered site user to extract sensitive customer data including PII and order records; no public exploit has been identified at time of analysis. This creates direct risk to customer privacy and potential regulatory exposure (GDPR, PCI-DSS compliance). No vendor-released patch identified at time of analysis, requiring immediate interim controls.
Restrict creation of new subscriber accounts; remove unused subscriber and contributor accounts; implement database query logging and real-time monitoring on tables containing customer PII and orders; deploy Web Application Firewall rules to detect and block SQL injection patterns targeting the plugin; disable the plugin if a functional alternative exists until patch is released.
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
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-63315
GHSA-h622-xrc2-7vh7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB