{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48261 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48261 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48261 is a high-severity vulnerability in MultiVendorX, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48261 and fix it if it is affected.\n\nWhat it is: CVE-2025-48261 is a high-severity vulnerability in MultiVendorX, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48261 in the wild and no public exploit code.\n\nAffected product: MultiVendorX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-48261/ (Markdown: https://insights.sbomify.com/CVE-2025-48261/index.md)","id":"CVE-2025-48261","markdown":"https://insights.sbomify.com/CVE-2025-48261/index.md","name":"CVE-2025-48261","record":{"aliases":["GHSA-gr9m-c25c-rj65"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can retrieve embedded sensitive data from MultiVendorX plugin responses, exposing confidential information to unauthorized users.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"multivendorx","vendor":"multivendorx"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"Insertion of Sensitive Information Into Sent Data vulnerability in MultiVendorX MultiVendorX dc-woocommerce-multi-vendor allows Retrieve Embedded Sensitive Data.This issue affects MultiVendorX: from n/a through \u003c= 4.2.22.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress MultiVendorX plugin \u003c= 4.2.22 - Sensitive Data Exposure Vulnerability","id":"CVE-2025-48261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Url Rewrite Analyzer plugin \u003c= 1.3.3 - Broken Access Control Vulnerability","id":"CVE-2025-48262"},"packages":[],"prev":{"headline":"WordPress GDPR CCPA Compliance Support plugin \u003c= 2.7.3 - Broken Access Control Vulnerability","id":"CVE-2025-48260"},"products":["MultiVendorX"],"published":"2025-06-09","related":[{"cvss_score":9.8,"headline":"Path traversal in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2025-0493","kev_date_added":null,"published":"2025-01-31"},{"cvss_score":9.8,"headline":"Missing authorization in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2024-8289","kev_date_added":null,"published":"2024-09-04"},{"cvss_score":7.1,"headline":"WordPress MultiVendorX Marketplace \u003c= 4.1.3 - Broken Access Control vulnerability","id":"CVE-2024-31304","kev_date_added":null,"published":"2024-06-09"},{"cvss_score":6.5,"headline":"WordPress MultiVendorX plugin \u003c= 4.2.22 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-48263","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":6.4,"headline":"Cross-site scripting in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2024-5259","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":6.3,"headline":"Cross-site request forgery in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2024-9943","kev_date_added":null,"published":"2024-10-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["MultiVendorX"]},"summary":"Attackers can retrieve embedded sensitive data from MultiVendorX plugin responses, exposing confidential information to unauthorized users.","url":"https://insights.sbomify.com/CVE-2025-48261/"}