dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-49924

HIGH · 7.2 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Josh Kohlbach Wholesale Suite woocommerce-wholesale-prices allows Privilege Escalation.This issue affects Wholesale Suite: from n/a through <= 2.2.4.2.

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

A privilege escalation vulnerability exists in the Wholesale Suite plugin's woocommerce-wholesale-prices component where incorrect privilege assignment allows lower-privileged users to gain elevated access. The vulnerability stems from insufficient permission checks in the wholesale pricing functionality.

MitigationUpdate Wholesale Suite to the latest version beyond 2.2.4.2. Conduct a security audit to verify no unauthorized privilege escalation occurred and ensure all user roles have correct permission configurations.

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 checks

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

  1. Confirm Wholesale Suite plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Wholesale Suite' or check via wp-content/plugins directory for the wholesale-suite folder. Note the installed version number displayed in the plugins list.
    Affected if The plugin is installed and the version is 2.2.4.2 or earlier, or if the version cannot be determined (unknown).
  2. Verify woocommerce-wholesale-prices component is active
    In WordPress admin, go to WooCommerce > Wholesale Prices > Settings, or check the active modules in Wholesale Suite settings. Confirm the wholesale pricing functionality is enabled.
    Affected if The woocommerce-wholesale-prices component is enabled and active on the site.
  3. Inspect user role capabilities for wholesale-related permissions
    Use a role editor plugin or query the wp_options table for option_name containing 'user_roles' to review capabilities assigned to each role. Specifically look for: manage_woocommerce, view_woocommerce_reports, wholesalePricingControls, and other wholesale-related capabilities.
    Affected if Lower-privileged roles (such as Customer, Subscriber, or Contributor) have capabilities typically reserved for Shop Manager or Administrator roles.
  4. Check for unauthorized role modifications
    Compare current role capabilities against a default/known-good baseline. Look for roles with unexpected elevated capabilities such as manage_options, edit_users, delete_users, or manage_woocommerce.
    Affected if Any non-administrator roles possess elevated capabilities that were not intentionally assigned.
  5. Review access logs for privilege escalation activity
    Examine WordPress audit logs, server access logs, or security plugins for events around wholesale price modifications, user role changes, or privilege escalation attempts. Look for actions performed by lower-privileged users.
    Affected if Audit logs show actions performed by users with role levels below Administrator that involve changing wholesale prices, user roles, or other privileged operations.

A user is affected if the Wholesale Suite plugin with woocommerce-wholesale-prices is installed at version 2.2.4.2 or earlier and the wholesale pricing component is enabled, particularly if lower-privileged roles have unexpected elevated capabilities.

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 Wholesale Suite to the latest version beyond 2.2.4.2. Conduct a security audit to verify no unauthorized privilege escalation occurred and ensure all user roles have correct permission configurations.

Recommended fix Moderate confidence

Latest version of Wholesale Suite plugin (version higher than 2.2.4.2)

  1. 1. Update the Wholesale Suite plugin (woocommerce-wholesale-prices) to the latest available version from the WordPress plugin repository or the vendor
  2. 2. After updating, verify that the privilege escalation vulnerability is resolved by reviewing the plugin changelog or release notes
  3. 3. Test that existing wholesale user roles and permissions function correctly after the update
  4. 4. Confirm that no unauthorized privilege changes have occurred by reviewing user roles in WooCommerce wholesale settings
Caveat Review plugin changelog for any breaking changes between 2.2.4.2 and the target upgrade version before updating in production

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49924 — 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-2025-49924 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