dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-27542

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Incorrect Privilege Assignment vulnerability in Rymera Web Co Pty Ltd. Woocommerce Wholesale Lead Capture woocommerce-wholesale-lead-capture allows Privilege Escalation.This issue affects Woocommerce Wholesale Lead Capture: from n/a through <= 2.0.3.1.

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 confidence

The WooCommerce Wholesale Lead Capture plugin versions 2.0.3.1 and below contains an Incorrect Privilege Assignment vulnerability allowing authenticated users to escalate their privileges beyond what should be permitted, potentially gaining administrative access to the WooCommerce wholesale lead capture system.

MitigationUpdate to the latest version of Woocommerce Wholesale Lead Capture once a patch is released. Until then, restrict user registration and role assignments, and monitor for unauthorized administrative accounts.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WooCommerce Wholesale Lead Capture' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Determine the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the WooCommerce Wholesale Lead Capture plugin and locate the version number displayed below the plugin name.
    Affected if The version displayed is 2.0.3.1 or any earlier version.
  3. Compare version against the affected range
    Reference the version number found in the previous step. The vulnerability affects versions up to and including 2.0.3.1.
    Affected if The installed version is 2.0.3.1 or lower.
  4. Review WordPress user accounts for unauthorized administrators
    Navigate to Users > All Users in the WordPress admin dashboard. Examine the list of users and their assigned roles, looking for any unexpected administrator accounts or suspicious role assignments.
    Affected if There are administrator accounts that were not created by known administrators, or existing user roles have been unexpectedly modified.
  5. Check plugin role/capability settings
    Navigate to the plugin settings page (usually under WooCommerce > Wholesale Lead Capture or a dedicated Wholesale settings area). Review any role assignment or capability configuration options to see if incorrect privilege escalation has been configured.
    Affected if Non-administrator users have been granted administrator-level capabilities or the role settings show unexpected privilege assignments.

Your environment is affected if the WooCommerce Wholesale Lead Capture plugin is active and the installed version is 2.0.3.1 or lower, or if unauthorized privilege changes are detected in user roles.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Woocommerce Wholesale Lead Capture once a patch is released. Until then, restrict user registration and role assignments, and monitor for unauthorized administrative accounts.

Recommended fix Moderate confidence

Version greater than 2.0.3.1 (check WordPress plugin repository for latest stable release)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate 'WooCommerce Wholesale Lead Capture' in the plugin list
  3. 3. Check the current installed version of the plugin
  4. 4. If the installed version is <= 2.0.3.1, update the plugin to the latest available version
  5. 5. After updating, verify the plugin version has been upgraded to confirm the patch was applied
  6. 6. Test that user privilege assignments function correctly to confirm the privilege escalation vulnerability has been resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27542 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27542 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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