Security readout for executives and security teams
Plain-English summary
WCFM Marketplace versions through 3.8.1 contain a critical SQL injection vulnerability that an unauthenticated remote attacker may reach over the network. Successful exploitation could expose sensitive marketplace database information and cause limited service disruption. The supplied sources do not identify confirmed active exploitation.
Executive priority
Treat this as an urgent remediation and exposure-assessment item, especially for public marketplace sites. The unauthenticated attack path and potential database disclosure justify immediate ownership and short timelines. Escalate if affected versions are present, while avoiding claims of an ongoing campaign without supporting evidence.
Technical view
CVE-2026-81286 is an unauthenticated SQL injection (CWE-89) in the WordPress WCFM Marketplace plugin through version 3.8.1. Its CVSS 3.1 score is 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L), indicating low-complexity remote access without credentials or user interaction, with high confidentiality and low availability impact.
Likely exposure
Internet-facing WordPress sites with WCFM Marketplace enabled at version 3.8.1 or earlier are the likely exposure group. The bundle provides no affected endpoint, configuration prerequisites, CPE mapping, or reliable installation prevalence. Confirm exposure through asset and plugin inventories rather than assumptions.
Exploitation context
The vulnerability is remotely reachable, requires neither authentication nor user interaction, and is rated low complexity. However, CVE-2026-81286 is not listed as KEV in the supplied bundle, and no supplied source confirms exploitation in the wild. Absence from KEV does not prove exploitation is absent.
Researcher notes
Public details in the supplied bundle are limited to the vulnerability class, affected version boundary, and CVSS vector. No vulnerable parameter, endpoint, proof of concept, root cause, fixed version, or compromise indicators are provided. The affected record also reports versions as “n/a,” so the description and Patchstack entry support the through-3.8.1 boundary.
Mitigation direction
- Inventory WordPress sites and identify enabled WCFM Marketplace versions.
- Prioritize internet-facing installations running version 3.8.1 or earlier.
- Check current WC Lovers or Patchstack guidance for a fixed version or official mitigation.
- Until guidance is confirmed, restrict exposure or disable the plugin where business impact permits.
- Preserve relevant web, application, database, and security logs for investigation.
Validation and detection
- Confirm the installed plugin version from trusted administrative or deployment records.
- Verify whether WCFM Marketplace is enabled on each identified WordPress site.
- Review vendor guidance and confirm the deployed version is outside the affected range.
- Inspect historical logs for anomalous unauthenticated requests and unusual database errors.
- Perform only authorized, non-destructive validation; the supplied sources identify no safe test procedure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-81286 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/wc-multivendor-marketplace/vulnerability/wordpress-wcfm-marketplace-plugin-3-8-1-sql-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.