CVE-2026-54838
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSubscriber SQL Injection in WC Vendors Marketplace <= 2.6.8 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in WC Vendors Marketplace plugin allows authenticated users with Subscriber role to inject malicious SQL queries through unspecified input parameters, potentially enabling data exfiltration or database manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WC Vendors Marketplace plugin is installedNavigate to WordPress admin dashboard > Plugins and locate WC Vendors Marketplace in the list of installed plugins. Note whether it is active or inactive.Affected if The plugin is installed and active, as only an active installation can be exploited.
-
Identify the installed plugin versionIn the Plugins list, click on the plugin name to view its details, or check the plugin header in the main PHP file for the 'Version' constant. Compare this version number to 2.6.9.Affected if The installed version is lower than 2.6.9, indicating the vulnerability is present in the codebase.
-
Verify Subscriber role exists and is activeGo to WordPress admin > Users > Roles, or use a role management plugin to list all user roles. Confirm that the Subscriber role is present and not disabled.Affected if The Subscriber role exists and is functional, as attackers require this role to exploit the SQL injection.
-
Check if any Subscriber-level users existIn WordPress admin > Users, filter or search for users with the Subscriber role. Count how many Subscriber accounts are present.Affected if There is at least one active Subscriber user account, which could be used by an attacker to inject malicious SQL.
-
Review access controls for vendor-related featuresNavigate to WC Vendors > Settings in the admin panel. Examine the options that control which user roles can access vendor dashboard features or submission forms.Affected if Subscriber role is granted permission to access vendor-facing pages or forms, providing the attack surface for SQL injection.
The environment is affected if WC Vendors Marketplace plugin version is below 2.6.9 AND the Subscriber role has any access to the plugin's frontend or dashboard features.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WC Vendors Marketplace plugin to version 2.6.9 or later to patch the SQL injection vulnerability.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54838 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54838 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data