CVE-2026-27541
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 · uneditedIncorrect Privilege Assignment vulnerability in Josh Kohlbach Wholesale Suite woocommerce-wholesale-prices allows Privilege Escalation.This issue affects Wholesale Suite: from n/a through <= 2.2.6.
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 confidenceThe Wholesale Suite woocommerce-wholesale-prices plugin <= 2.2.6 contains an Incorrect Privilege Assignment vulnerability allowing authenticated users to escalate their privileges beyond what their role should permit. This likely involves improper validation of user capabilities when accessing wholesale pricing functions or administrative features.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed plugin versionNavigate to WordPress admin > Plugins > WooCommerce Wholesale Prices and read the version number displayed, or inspect the plugin main file header for the 'Version' fieldAffected if The installed version is 2.2.6 or lower
-
Verify admin user accountsGo to WordPress Users menu and review all accounts with Administrator role. Cross-reference creation dates and email addresses against expected registrationsAffected if There are administrator accounts you did not create or that belong to non-admin users
-
Test wholesale pricing accessLog in as a low-privilege user (subscriber, customer, or shop manager) and attempt to access WooCommerce > Wholesale Prices settings or wholesale pricing configuration pagesAffected if A non-administrator user can view or modify wholesale pricing settings without proper authorization
-
Audit user capabilitiesUse a role management plugin or WP-CLI 'wp user list --role=administrator' to enumerate all admin accounts, then compare against your organization user rosterAffected if Unexpected or unauthorized users hold administrator-level capabilities
You are affected if the plugin version is 2.2.6 or lower AND you have unauthorized administrative accounts or lower-privileged users can access wholesale pricing administrative functions.
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 dataUpgrade to a patched version of the Wholesale Suite plugin that properly enforces role-based access controls. Until patched, restrict user registrations and monitor for unauthorized administrative accounts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27541 — 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-27541 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