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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
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
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
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Multivendorx
View allBroken object-level authorization in the MultiVendorX WordPress plugin before 5.0.11 allows any authenticated vendor (St
Privilege escalation in MultiVendorX WordPress plugin before 5.0.16 allows authenticated vendor-role users to grant admi
Broken access control in the MultiVendorX WordPress plugin (versions 5.0.0 through 5.0.15) allows any authenticated user
The Product Catalog Mode For WooCommerce WordPress plugin before 5.0.3 does not properly authorize settings updates or e
The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privi
Unauthenticated information disclosure in the MultiVendorX WordPress plugin (versions prior to 5.0.15) exposes sensitive
Missing Authorization vulnerability in MultiVendorX Product Catalog Enquiry for WooCommerce by MultiVendorX.0.5. Rated c
Missing Authorization vulnerability in MultiVendorX WC Marketplace.1.3. Rated high severity (CVSS 8.8), this vulnerabili
Unauthenticated broken access control in the MultiVendorX WordPress plugin (versions 5.0.10 and earlier) exposes restric
Authenticated vendor (store_owner) accounts in the MultiVendorX WooCommerce plugin through 5.0.19 can silently overwrite
Insecure Direct Object Reference (IDOR) in the MultiVendorX WordPress plugin before 5.0.11 exposes confidential financia
Unauthenticated privilege escalation in the Product Catalog Enquiry for WooCommerce by MultiVendorX WordPress plugin (ve
EUVD-2025-17536
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB