CVE-2023-37972
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in MultiVendorX Product Stock Manager & Notifier for WooCommerce.This issue affects Product Stock Manager & Notifier for WooCommerce: from n/a through 2.0.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 confidenceAn information disclosure vulnerability in the MultiVendorX Product Stock Manager & Notifier for WooCommerce plugin allows unauthenticated or unauthorized actors to access sensitive product stock data. The specific flaw appears to involve improper access controls in the stock management functionality, potentially exposing inventory levels, product details, or notification settings to unauthorized users.
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< 2.0.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > MultiVendorX Product Stock Manager & Notifier For Woocommerce and note the version number displayed. Alternatively, inspect the plugin header in wp-content/plugins/dc-woocommerce-multi-vendor/includes/class-mvx.php or the main plugin file to find the Version: X.X.X field.Affected if The displayed version number is lower than 2.0.2 (for example, 2.0.1, 2.0.0, 1.x.x, or no version shown)
-
Identify stock manager AJAX or API endpointsSearch the plugin directory for files handling stock management requests. Look in wp-content/plugins/dc-woocommerce-multi-vendor/ for PHP files containing terms like 'stock_manager', 'stock_notifier', 'get_stock', or 'ajax' that relate to inventory. Common paths may include classes handling frontend AJAX calls or REST API routes.Affected if The plugin contains files or functions that handle stock data retrieval without visible capability checks or nonce verification for unauthenticated users
-
Test unauthenticated access to stock dataIf the site allows external probe, send a direct request to known plugin AJAX endpoints (such as /wp-admin/admin-ajax.php?action=mxv_get_stock_details or similar) without providing authentication cookies or valid nonces. Use a tool like curl or Burp Suite to observe the response.Affected if The server returns JSON or XML containing product stock levels, notification settings, or inventory details without requiring login credentials (response contains product IDs, stock quantities, or vendor information)
-
Review access control implementation in stock classesExamine the PHP class files responsible for stock management (typically in classes directory under the plugin folder). Search for functions that fetch or display stock information and verify they include current_user_can() checks, capability verification, or nonce validation before returning data.Affected if Stock data retrieval functions lack proper capability checks (like 'manage_options' or 'edit_products') or do not verify user authentication before outputting sensitive inventory data
A user is affected if the MultiVendorX Product Stock Manager plugin version is below 2.0.2 AND the stock management endpoints are accessible without authentication or proper authorization checks.
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.
dbcve · scoped2.0.2
Upgrade to version 2.0.2 or later, which contains the security fix. If immediate patching is not possible, restrict access to the affected plugin endpoints via web server configuration or implement additional authentication requirements until the update can be applied.
2.0.2
- Update the Product Stock Manager & Notifier For WooCommerce plugin to version 2.0.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-37972 — 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-2023-37972 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