Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running WCFM Marketplace
-
DeliverySend crafted request to vulnerable parameter
-
ExploitInject SQL into backend query
-
ExecutionExtract user/order database records
-
ImpactEscalate via stolen admin 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 | Exploitation requires only that the WCFM Marketplace plugin (<= 3.8.1) is installed and network-reachable on a WordPress site; the CVSS vector is AV:N/AC:L/PR:N/UI:N, so no authentication, no user interaction, and no special non-default configuration are indicated. The practical limiting factor is that the vulnerable request parameter/endpoint is not named in the advisory, so an attacker must identify the specific injectable input; sites not running WCFM Marketplace, or already upgraded past 3.8.1, are not exposed. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes low-effort, remote, unauthenticated exploitation, which is the highest-urgency profile for an internet-facing WordPress plugin; the 9.3 base score is driven by C:H (database disclosure) plus scope change, with I:N and only A:L. Unauthenticated WordPress plugin SQLi cataloged by Patchstack is a class that is frequently weaponized and mass-scanned once details or a POC surface, so exposure should be treated as time-sensitive even though there is currently no public exploit and no CISA KEV listing. EPSS was not provided in the input, so probabilistic exploitation likelihood cannot be quantified here. The main uncertainty is the affected parameter/endpoint, which the description does not name; defenders should assume any reachable WCFM request could be the vector and prioritize patching accordingly. |
| Exploit ScenarioDerived | An attacker scanning for WordPress sites running WCFM Marketplace sends a crafted HTTP request with a malicious SQL payload to a vulnerable plugin parameter, without needing an account. The injected query extracts administrator password hashes and customer/order records from the shared database, enabling credential cracking or direct data theft. No public POC is identified yet, but the low-complexity unauthenticated vector makes reliable exploitation straightforward once the endpoint is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
SQL injection in the WCFM Marketplace WordPress plugin (versions 3.8.1 and earlier) lets remote unauthenticated attackers inject arbitrary SQL into backend database queries. Per the CVSS vector this is exploitable over the network without privileges or user interaction, and the changed scope with high confidentiality impact indicates database contents can be read across the WordPress store's data. Reported by Patchstack; no public exploit code or active exploitation has been identified at time of analysis.
RemediationAI
Upgrade WCFM Marketplace to a release later than 3.8.1 once the vendor publishes a fixed build; the provided data lists 3.8.1 as the last vulnerable version but does not confirm the exact patched version, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wc-multivendor-marketplace/vulnerability/wordpress-wcfm-marketplace-plugin-3-8-1-sql-injection-vulnerability) and the WC Lovers changelog for the corrected release before deploying. Until patched, deploy a WAF or virtual-patching rule (Patchstack, Wordfence, or equivalent) to filter SQL-injection payloads against WCFM endpoints, and restrict access to marketplace/vendor functionality where feasible - note WAF rules can be bypassed and may false-positive on legitimate vendor queries. Additionally, apply least-privilege to the WordPress database user and take a verified backup so post-exploitation data theft can be scoped if compromise is suspected.
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
WCFM Marketplace (plugin slug wc-multivendor-marketplace, CPE cpe:2.3:a:wc_lovers:wcfm_marketplace) is a widely used multivendor/marketplace extension for WooCommerce on WordPress, adding vendor stores, product management, and commission handling. The root cause is CWE-89 (SQL Injection): user-controlled input reaches a database query without proper parameterization or sanitization, so an attacker can alter the query structure. Because WordPress plugins share the single site database, a successful injection can reach WordPress core tables (e.g. wp_users) and WooCommerce order/customer data, which is consistent with the CVSS scope-change (S:C) rating.
Know when Wcfm 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
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Remote unauthenticated SQLi (AV:N/AC:L/PR:N/UI:N) with database read (C:H) and possible limited write/tampering (I:L) across the shared DB (S:C); no availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated SQL Injection in WCFM Marketplace <= 3.8.1 versions.
Executive ViewAI
The WCFM Marketplace WordPress plugin (versions 3.8.1 and earlier) contains a critical unauthenticated SQL injection vulnerability allowing remote attackers to extract sensitive database contents without authentication. Organizations running this multivendor marketplace plugin risk exposure of customer data, payment information, and store configuration, creating potential liability under PCI DSS, GDPR, and other regulatory frameworks.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) disable plugin if business functions can tolerate suspension, (2) restrict database user permissions to read-only on non-sensitive tables and block direct access to customer/payment tables, (3) deploy WAF signatures blocking common SQL injection syntax, (4) enable database encryption at rest and in transit, (5) implement comprehensive database audit logging, and (6) segment the WordPress application server from other infrastructure.
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.
More in Wcfm Marketplace
View allMissing authorization in WCFM Marketplace WordPress plugin before 3.8.2 allows unauthenticated users to submit refund re
The WCFM Marketplace plugin for WordPress is vulnerable to unauthorized modification and access of data in versions up t
SQL injection in the WCFM Marketplace plugin for WordPress allows authenticated high-privilege users (e.g., administrato
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WC Lovers WCFM Mar
Stored cross-site scripting in WCFM Marketplace (WordPress WooCommerce multivendor plugin) through version 3.8.2 allows
The WCFM Marketplace plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'wcfm_stores' shortcode in ve
The WCFM Marketplace plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including,
EUVD-2026-69923
GHSA-7g84-hf36-28w5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB