dbcve.org
Wholesale SuiteWordPress extension · Rymera

CVE-2022-41640

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-09
Fix available
A fix is available. Upgrade to 2.1.5.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (subscriber+) Stored Cross-Site Scripting (XSS) vulnerability in Rymera Web Co Wholesale Suite plugin <= 2.1.5 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 confidence

Authenticated stored XSS vulnerability in Rymera Web Co Wholesale Suite plugin affecting versions 2.1.5 and below. Users with subscriber-level permissions or higher can inject malicious scripts that persist on the server and execute when other users access the affected content.

MitigationUpdate Wholesale Suite plugin to version newer than 2.1.5; if no update available, disable the plugin until a patched version is released.

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.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Identify Wholesale Suite plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins. Look for 'Wholesale Suite' or 'Rymera Wholesale Suite' in the list. Note the version number displayed under the plugin name.
    Affected if Plugin is listed with version below 2.1.5.1
  2. Confirm plugin version via file inspection
    If available, inspect the main plugin file (typically wholesale-suite.php or similar in wp-content/plugins/ wholesale-suite/) and locate the 'Version' header in the plugin comments at the top of the file.
    Affected if Version header reads lower than 2.1.5.1
  3. Verify plugin is active
    In WordPress admin Plugins page, check if the Wholesale Suite plugin shows as 'Active'. Alternatively, check the wp_options table for option_name containing 'active_plugins'.
    Affected if Plugin is currently active and version is below 2.1.5.1
  4. Assess user role exposure
    Navigate to WordPress Users section. Review existing user accounts and their assigned roles. This vulnerability is exploitable by any user with Subscriber-level access or higher.
    Affected if One or more active user accounts have Subscriber, Contributor, Author, Editor, or Administrator role AND plugin version is below 2.1.5.1

Your environment is affected if the Wholesale Suite plugin is installed, active, and running a version lower than 2.1.5.1 with at least one user account having subscriber-level permissions or higher.

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
Upgrade available Upgrade to 2.1.5.1 or later
Fixed in 2.1.5.1
Interim mitigation

Update Wholesale Suite plugin to version newer than 2.1.5; if no update available, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

2.1.5.1

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find the Wholesale Suite plugin (by Rymera Web Co)
  4. 4. Check the current version to confirm it is <= 2.1.5
  5. 5. If an update is available, click 'Update Now' to update to version 2.1.5.1 or later
  6. 6. If no automatic update is available, manually download version 2.1.5.1 or the latest version from the WordPress Plugin Repository
  7. 7. Deactivate and delete the current plugin, then upload and install the new version
  8. 8. Reactivate the plugin after installation

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

Fix this in Wholesale Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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