dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-50899

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 MultiVendorX Product Catalog Enquiry for WooCommerce by MultiVendorX allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Product Catalog Enquiry for WooCommerce by MultiVendorX: from n/a through 5.0.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

This is a missing authorization vulnerability in the MultiVendorX Product Catalog Enquiry for WooCommerce plugin. The plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels to access functionality they should not have permission to use.

MitigationImplement proper authorization checks (capability verification) on all sensitive functions and AJAX actions within the plugin. Update to the latest patched version when available and verify that all admin and user-facing actions validate user permissions before execution.

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

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

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 plugin installation
    Navigate to WordPress admin > Plugins and verify that the 'MultiVendorX Product Catalog Enquiry for WooCommerce' plugin is installed and active
    Affected if the plugin is installed and active in WordPress
  2. Identify installed version
    In WordPress admin > Plugins, locate the MultiVendorX Product Catalog Enquiry plugin and record the version number displayed
    Affected if the installed version lacks the security patch for CVE-2023-50899 (version comparison required)
  3. Inspect AJAX action registrations
    Access the plugin directory via file manager or FTP, then examine the main plugin file and look for add_action('wp_ajax_...) calls to identify exposed AJAX endpoints
    Affected if AJAX actions lack capability checks (missing current_user_can() or similar authorization calls before executing)
  4. Review sensitive function authorization
    Examine PHP files in the plugin for functions that handle enquiry submissions, data retrieval, or admin-level operations; verify each contains proper authorization logic
    Affected if sensitive functions execute without verifying user permissions or validating nonce tokens
  5. Test unauthorized access potential
    If feasible, attempt to access plugin functionality from a non-privileged user account (subscriber or guest) to confirm if access controls are enforced
    Affected if lower-privileged users can access functionality intended for administrators or vendors

A user is affected if the MultiVendorX Product Catalog Enquiry plugin is installed and its AJAX actions or sensitive functions lack proper capability verification before execution.

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

Implement proper authorization checks (capability verification) on all sensitive functions and AJAX actions within the plugin. Update to the latest patched version when available and verify that all admin and user-facing actions validate user permissions before execution.

Recommended fix Moderate confidence

Version newer than 5.0.2 (check WordPress plugin repository for latest stable release)

  1. Check the current version of the MultiVendorX Product Catalog Enquiry plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate 'Product Catalog Enquiry for WooCommerce by MultiVendorX' and note the current version number
  4. Visit the official WordPress plugin repository or MultiVendorX website to check for a version newer than 5.0.2 that includes the security fix
  5. If a newer version exists, update the plugin through WordPress admin or download and install the updated version manually
  6. After updating, verify the plugin is functioning correctly and test the enquiry functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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