Skip to main content

WC Vendors Marketplace CVE-2026-66625

| EUVDEUVD-2026-81507 HIGH
SQL Injection (CWE-89)
2026-09-17 Patchstack GHSA-c5c2-pmcv-c437
7.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain WP administrator access
  2. Delivery
    Reach vulnerable marketplace admin endpoint
  3. Exploit
    Inject crafted SQL payload
  4. Execution
    Query executes against database
  5. Impact
    Exfiltrate cross-scope data

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

Exploitation requires an authenticated WordPress administrator account (PR:H) on a site running WC Vendors Marketplace version 2.7.2.1 or earlier; the attacker reaches an admin-side marketplace parameter that is vulnerable to SQL injection. No user interaction is needed (UI:N) and it is reachable over the network (AV:N), but the administrator-level authentication gate is the dominant limiting factor - this is not exploitable by unauthenticated visitors, vendors, or ordinary customers. Because a WP administrator already has full database and code-execution capability through normal admin functionality, the practical exposure is largely limited to insider misuse or post-compromise use of a hijacked admin session.

Impact

This is a high-CVSS-but-modest-real-risk issue driven almost entirely by the privilege requirement. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L, score 7.6) explicitly encodes PR:H, and the vulnerability title itself is 'Administrator SQL Injection' - meaning the attacker must already hold administrator (or equivalently high) privileges in the WordPress/WooCommerce instance before the flaw is reachable. An actor with WP administrator rights can already read and modify the entire database and execute PHP via plugins/themes, so the marginal capability this SQLi grants is limited; the primary added value is direct, app-logic-bypassing query access. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so exploitation status is: no public exploit identified at time of analysis. There is no SSVC decision data supplied. The one internal tension worth flagging: the vendor sets S:C and C:H yet I:N and A:L, which is an unusual impact profile for SQL injection (injection typically permits both read and write) - this likely reflects a read-oriented injection sink, but the I:N/A:L split should be verified against the Patchstack advisory. Net: legitimate to patch, but not an emergency for internet-facing exposure because pre-existing admin access is the gate.

Exploit ScenarioDerived

An authenticated administrator (or a lower-privileged actor who has already compromised an admin account, e.g. via a separate phishing or credential-reuse chain) submits crafted input to a vulnerable marketplace admin parameter that is concatenated into a SQL query. The injected query returns database contents outside the plugin's intended scope (customer, order, and vendor data). No public exploit code is identified in the supplied intelligence, and the network attack vector requires no user interaction once admin access 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 – Sep 17, 2026

SQL injection in the WC Vendors Marketplace WordPress plugin (versions up to and including 2.7.2.1) allows an authenticated WordPress administrator to inject arbitrary SQL through an admin-side marketplace parameter, putting the site's database contents at risk of disclosure. The administrator-level privilege gate (PR:H) is the dominant limiting factor: administrator accounts already hold full database and code-execution capability, so the realistic exposure is largely insider misuse or reuse of a hijacked admin session rather than attacker escalation from a low-privileged user. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the issue is tracked as EUVD-2026-81507 following disclosure by Patchstack.

RemediationAI

The provided intelligence does not reference a fixed release, so patch availability is unconfirmed for CVE-2026-66625; consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wc-vendors/vulnerability/wordpress-wc-vendors-marketplace-plugin-2-7-2-1-sql-injection-vulnerability?_s_id=cve) and the WC Vendors Marketplace changelog for a build newer than 2.7.2.1 and upgrade as soon as one is published, since no vendor-released patch is identified at time of analysis. Because exploitation requires an authenticated administrator, the most effective compensating controls target the admin role itself: prune unused or stale administrator accounts, enforce unique credentials plus multifactor authentication for every admin login, and rotate administrator passwords and session tokens if a hijacked session is suspected - these measures reduce the attack surface but do nothing against a malicious insider or an attacker who already holds valid admin credentials. Interim application-level mitigation is possible by deploying WAF or virtual-patching rules that reject SQL metacharacters in WC Vendors admin marketplace parameters, at the cost of potential false positives that break legitimate admin workflows and with the caveat that an administrator can typically bypass such filters; alternatively, deactivating the plugin eliminates the exposure entirely while removing all marketplace functionality. As a detection measure, log and review admin-side requests to the plugin's admin endpoints for anomalous SQL syntax and monitor the database account for unexpected query patterns, since the plugin's own admin traffic is the only place this injection can originate.

Affected VersionsENISA

WC Vendors Marketplace n/a ≤2.7.2.1

Affected Packages

euvd wc_vendors_marketplace 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 affected component is a WordPress plugin, WC Vendors Marketplace, which extends WooCommerce with multi-vendor marketplace functionality and, per the CPE cpe:2.3:a:wcvendors:wc_vendors_marketplace:*:*:*:*:*:*:*:*, applies across the plugin's published version line (EUVD specifies the affected range as 2.7.2.1 and earlier). The root cause class is CWE-89, improper neutralization of special elements used in an SQL command: an admin-side marketplace parameter is concatenated into a SQL statement without adequate parameterization or use of WordPress's prepared-statement helpers, so a request from an administrator session can alter the query structure. Here the vendor-assigned vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L, 7.6) and the independent assessment (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L) agree on network reachability, low attack complexity, the PR:H administrator prerequisite and no user interaction, but diverge on scope (changed vs. unchanged) and on whether integrity impact is absent or low. That divergence, combined with the fact that a WordPress administrator can already read and modify the database directly through normal admin functionality, is why the privilege requirement rather than the raw score should drive prioritization.

Know when Wc Vendors Marketplace 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.6 HIGH
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 6.0 MEDIUM

Administrator privilege gives PR:H; SQLi enables broad DB read (C:H) with some write/availability effect (I:L/A:L); scope kept U as injection stays within the app's own database.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Administrator SQL Injection in WC Vendors Marketplace <= 2.7.2.1 versions.

Executive ViewAI

Why It Matters

The WC Vendors Marketplace WordPress plugin, versions up to and including 2.7.2.1, carries a high-severity SQL injection that could expose marketplace site database contents, but only to an authenticated administrator-level user. Because administrator accounts already wield extensive control and no public exploit has been identified at time of analysis, the practical business risk is most likely tied to insider misuse or a compromised admin session rather than external mass exploitation. Leadership should prioritize admin access governance, monitoring, and contingency planning while no vendor patch is available.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include restricting administrator accounts to trusted personnel, enforcing MFA, applying IP allowlisting/VPN for admin access, removing dormant admin accounts, monitoring admin and database activity for SQL injection patterns, deploying virtual patching or WAF rules for the WC Vendors Marketplace admin parameters, and temporarily disabling the plugin on non-critical sites until a vendor fix is available.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Medium
popular WooCommerce multi-vendor marketplace plugin, tens of thousands of installs
Data Quality
3 sources
Confidence: Low

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· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

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

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

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