dbcve.org
Wholesale SuiteWordPress extension · Rymera

CVE-2022-34344

HIGH · 8.8 CVSS v3.1 Published 2024-01-08
Fix available
A fix is available. Upgrade to after 2.1.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Rymera Web Co Wholesale Suite – WooCommerce Wholesale Prices, B2B, Catalog Mode, Order Form, Wholesale User Roles, Dynamic Pricing & More.This issue affects Wholesale Suite – WooCommerce Wholesale Prices, B2B, Catalog Mode, Order Form, Wholesale User Roles, Dynamic Pricing & More: from n/a through 2.1.5.

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 missing authorization vulnerability in the Wholesale Suite plugin for WooCommerce allows authenticated users to access functionality they shouldn't have permission to access. This broken access control could enable unauthorized manipulation of wholesale pricing, user roles, or B2B configurations depending on the specific unprotected endpoint.

MitigationUpdate the plugin to the latest version which should contain the authorization fix. If no update is available, implement custom authorization checks on all sensitive plugin functions and restrict access based on user roles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wholesale SuiteWordPress extension
Affected:<= 2.1.5

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Wholesale Suite plugin is installed
    Check your WordPress installation under wp-content/plugins/ for the 'wholesale-suite' or 'rymera-wholesale-suite' directory, or list installed plugins via WP admin panel
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Determine the installed plugin version
    Access the plugin settings page in WooCommerce/WP admin, or inspect the plugin's main PHP file (usually in the plugin root) for the 'Version' header comment, or check the plugin row in the WordPress Plugins list
    Affected if The reported version number is 2.1.5 or lower (e.g., 2.1.4, 2.1.3, 2.0.x, etc.)
  3. Confirm the plugin handles wholesale pricing or B2B functions
    Review the plugin's active features in WooCommerce > Wholesale Suite settings; check if wholesale user roles, pricing tables, or B2B configurations are enabled
    Affected if Wholesale pricing, B2B features, or wholesale user role management modules are active
  4. Check for sensitive endpoint exposure
    Audit your site's REST API endpoints and admin AJAX actions related to the wholesale plugin (typically under /wp-json/wholesale/ or admin-ajax.php?action=wholesale_*), or review server access logs for unauthorized access attempts to wholesale-related endpoints
    Affected if Unprotected endpoints accept requests from authenticated users without proper role/capability checks

You are affected if the Rymera Wholesale Suite plugin is installed at version 2.1.5 or lower and the wholesale pricing, B2B configuration, or user role management features are active and accessible to lower-privileged authenticated users.

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.

From vendor data
Upgrade available Upgrade to a release after 2.1.5
Interim mitigation

Update the plugin to the latest version which should contain the authorization fix. If no update is available, implement custom authorization checks on all sensitive plugin functions and restrict access based on user roles.

Fix this in Wholesale Suite 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 the upgrade done

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-2022-34344 — 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-2022-34344 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