dbcve.org
MultivendorxWordPress extension

CVE-2025-48263

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-19
Fix available
A fix is available. Upgrade to 4.2.23 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in MultiVendorX MultiVendorX dc-woocommerce-multi-vendor allows Stored XSS.This issue affects MultiVendorX: from n/a through <= 4.2.22.

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 stored Cross-Site Scripting (XSS) vulnerability exists in the MultiVendorX plugin for WooCommerce. Attackers can inject malicious JavaScript through vendor input fields that gets persistently stored and executed when other users view the affected pages. This stems from improper input sanitization during web page generation.

MitigationUpdate MultiVendorX to the latest version once available, or apply proper input validation and output escaping using WordPress sanitization functions (esc_html, esc_attr, wp_kses) to all user-supplied vendor data before rendering.

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
MultivendorxWordPress extension
Affected:< 4.2.23

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. Check MultiVendorX plugin version
    In WordPress admin, go to Plugins > Installed Plugins > MultiVendorX and view the version number. Alternatively, check the plugin header in wp-content/plugins/woocommerce-multivendorx/mvx-plugin.php for the 'Version' comment.
    Affected if The installed version is lower than 4.2.23 (e.g., 4.2.22, 4.2.0, etc.)
  2. Verify vendor functionality is active
    In WordPress admin, go to MultiVendorX > Settings and confirm vendor registration or vendor dashboard is enabled. Also check if any vendors exist under Users > All Users with vendor roles.
    Affected if Vendor features are enabled and at least one vendor user account exists in the system
  3. Inspect vendor profile fields for stored content
    In WordPress admin, go to MultiVendorX > All Vendors and review each vendor's profile fields (Store Name, Shop Description, Address, etc.) for any unusual script tags, iframe elements, or event handlers like onload, onerror, or onclick.
    Affected if Any vendor profile contains raw HTML tags, script elements, or JavaScript event handlers that appear unescaped when viewed in the page source
  4. Check vendor product pages for unescaped content
    View the source code of a vendor shop page (vendor store page) and a vendor product listing. Search for raw <script> tags, javascript: URLs, or event attributes that originated from vendor-supplied fields.
    Affected if Vendor-supplied data (store name, product descriptions, vendor bio) renders as raw HTML/JavaScript instead of being escaped

You are affected if MultiVendorX version is below 4.2.23 AND vendor functionality is active, with vendor input fields displaying unescaped HTML content.

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 4.2.23 or later
Fixed in 4.2.23
Interim mitigation

Update MultiVendorX to the latest version once available, or apply proper input validation and output escaping using WordPress sanitization functions (esc_html, esc_attr, wp_kses) to all user-supplied vendor data before rendering.

Recommended fix High confidence

MultiVendorX version 4.2.23 or later

  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 MultiVendorX plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 4.2.23 or later.
  5. 5. Alternatively, download MultiVendorX version 4.2.23 from the WordPress plugin repository or your account.
  6. 6. Verify the updated version number reflects 4.2.23 or higher.
  7. 7. Test vendor functionality to ensure the update did not break existing workflows.

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

Fix this in Multivendorx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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