Skip to main content

Multivendorx EUVDEUVD-2025-17536

| CVE-2025-48261 HIGH
Insertion of Sensitive Information Into Sent Data (CWE-201)
2025-06-09 audit@patchstack.com
7.5
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
Impact

The CVSS 3.1 vector (7.5 High) reflects a significant confidentiality impact (C:H) with no integrity or availability compromise, consistent with information disclosure. The attack complexity is low (AC:L), requires no privileges (PR:N), and requires no user interaction (UI:N), making exploitation trivial from a technical standpoint. The network attack vector (AV:N) means any internet-connected instance is at risk. Without explicit EPSS scores or KEV confirmation provided, the real-world risk depends on: (1) whether MultiVendorX instances are commonly internet-exposed, (2) the criticality of data leaked (customer PII, payment tokens, admin credentials), and (3) deployment prevalence. For a multi-vendor marketplace platform, exposed customer data or vendor credentials represent significant business and compliance risk (GDPR, PCI-DSS). The absence of reported active exploitation does not diminish risk; low-complexity remote unauthenticated attacks on information disclosure typically see swift weaponization once disclosed. This should be treated as a priority patch candidate, particularly for production instances.

Exploit ScenarioDerived

An unauthenticated attacker discovers a publicly accessible MultiVendorX API endpoint (e.g., /api/products, /api/vendors, or /api/cart) that returns product or vendor data. Due to CWE-201, the API response includes unintended sensitive fields such as internal vendor IDs, payment processor tokens, admin email addresses, or API keys used for third-party integrations. The attacker makes simple HTTP GET requests to enumerate endpoints and extract this data without authentication (PR:N, UI:N). With leaked API keys or credentials, the attacker pivots to access admin panels, exfiltrate customer databases, or compromise integrated payment systems. The attack requires no special tools (AC:L) and can be performed by any network-connected party, making it suitable for automated reconnaissance or opportunistic exploitation during pre-compromise reconnaissance. A POC would likely consist of curl commands to call affected endpoints and demonstrate sensitive data disclosure in responses.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

CVE-2025-48261 is an information disclosure vulnerability in MultiVendorX that allows unauthenticated remote attackers to retrieve sensitive data embedded within sent data through a network-accessible interface. The vulnerability affects MultiVendorX versions up to and including 4.2.22, with a CVSS score of 7.5 indicating high confidentiality impact. While no active KEV or public POC details were provided in the available intelligence, the network-accessible attack vector (AV:N) and lack of privilege requirements (PR:N) make this a material risk for exposed instances.

RemediationAI

Immediate actions: (1) Upgrade MultiVendorX to the first patched version beyond 4.2.22 (likely 4.2.23 or later, pending vendor release). (2) If patched version is not yet available, implement network-level controls: restrict API endpoint access to authenticated/trusted sources, deploy WAF rules to filter sensitive data from responses, and disable unused API endpoints. (3) Review recent API response logs for evidence of sensitive data exfiltration (API keys, tokens, user IDs in response bodies). (4) Rotate any exposed credentials, API keys, or tokens discovered in logs. (5) Monitor official MultiVendorX security advisories and vendor GitHub/security portal for patch release and detailed remediation guidance. (6) Apply patches in a controlled staging environment first to validate compatibility with custom extensions or integrations.

Affected VersionsENISA

MultiVendorX n/a ≤4.2.22

Affected Packages

euvd multivendorx no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability is rooted in CWE-201 (Insertion of Sensitive Information Into Sent Data), a class of weakness where applications inadvertently include sensitive information in data transmissions that can be intercepted or retrieved by unauthorized parties. In the context of MultiVendorX (a multi-vendor marketplace platform), the flaw likely exists in API responses, data serialization, or cached content mechanisms where sensitive fields (API keys, internal identifiers, user tokens, or configuration data) are exposed in responses sent to unauthenticated clients. The AV:N and AC:L vectors indicate the vulnerability is exploitable over the network without special conditions, suggesting it may be present in default API endpoints or publicly accessible data retrieval functions. The issue affects MultiVendorX through version 4.2.22, indicating the vendor has released or plans to release patched versions beyond this threshold.

Know when Multivendorx gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Insertion of Sensitive Information Into Sent Data vulnerability in MultiVendorX MultiVendorX allows Retrieve Embedded Sensitive Data. This issue affects MultiVendorX: from n/a through 4.2.22.

Executive ViewAI

Why It Matters

CVE-2025-48261 affects MultiVendorX versions up to 4.2.22 and allows attackers to extract sensitive data embedded in outbound communications. With no patch currently available and a 7.5 CVSS severity rating, organizations running vulnerable versions face immediate risk of data exposure through this information disclosure vulnerability.

Business Impact: High
Compensating Controls

Implement network segmentation to restrict outbound communication from MultiVendorX servers to only required endpoints; deploy Web Application Firewall (WAF) rules to inspect and filter outbound data for sensitive information patterns (API keys, credentials, PII); enable data loss prevention (DLP) tools on network egress points; disable unnecessary features or APIs in MultiVendorX if feasible; implement strict outbound firewall rules limiting destination IPs and ports; increase monitoring and alerting on all data leaving MultiVendorX systems; consider temporary operational restrictions until patch availability confirmed.

Threat Intelligence Overview

EPSS Score
0.1%
Top 77% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-16605 HIGH POC
7.2 Aug 05

Broken object-level authorization in the MultiVendorX WordPress plugin before 5.0.11 allows any authenticated vendor (St

CVE-2026-74925 HIGH POC
7.2 Sep 11

Privilege escalation in MultiVendorX WordPress plugin before 5.0.16 allows authenticated vendor-role users to grant admi

CVE-2026-74926 HIGH POC
7.1 Sep 16

Broken access control in the MultiVendorX WordPress plugin (versions 5.0.0 through 5.0.15) allows any authenticated user

CVE-2023-5348 MEDIUM POC
6.1 Dec 18

The Product Catalog Mode For WooCommerce WordPress plugin before 5.0.3 does not properly authorize settings updates or e

CVE-2024-8289 CRITICAL
9.8 Sep 04

The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privi

CVE-2026-74927 MEDIUM POC
5.3 Sep 02

Unauthenticated information disclosure in the MultiVendorX WordPress plugin (versions prior to 5.0.15) exposes sensitive

CVE-2024-25929 CRITICAL
9.1 Jun 09

Missing Authorization vulnerability in MultiVendorX Product Catalog Enquiry for WooCommerce by MultiVendorX.0.5. Rated c

CVE-2024-31304 HIGH
8.8 Jun 09

Missing Authorization vulnerability in MultiVendorX WC Marketplace.1.3. Rated high severity (CVSS 8.8), this vulnerabili

CVE-2026-66441 HIGH
7.5 Aug 13

Unauthenticated broken access control in the MultiVendorX WordPress plugin (versions 5.0.10 and earlier) exposes restric

CVE-2026-108695 HIGH
7.1 Oct 11

Authenticated vendor (store_owner) accounts in the MultiVendorX WooCommerce plugin through 5.0.19 can silently overwrite

CVE-2026-16746 LOW POC
2.7 Aug 05

Insecure Direct Object Reference (IDOR) in the MultiVendorX WordPress plugin before 5.0.11 exposes confidential financia

CVE-2026-81792 MEDIUM
6.5 Sep 08

Unauthenticated privilege escalation in the Product Catalog Enquiry for WooCommerce by MultiVendorX WordPress plugin (ve

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy