{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9943 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9943 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9943 is a medium-severity vulnerability in wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-9943 and fix it if it is affected.\n\nWhat it is: CVE-2024-9943 is a medium-severity vulnerability in wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-9943 in the wild and no public exploit code.\n\nAffected product: wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions. 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-2024-9943/ (Markdown: https://insights.sbomify.com/CVE-2024-9943/index.md)","id":"CVE-2024-9943","markdown":"https://insights.sbomify.com/CVE-2024-9943/index.md","name":"CVE-2024-9943","record":{"aliases":["GHSA-wm4f-jr24-wgqm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into updating vendor details, creating accounts, or deleting users via forged requests in the MultiVendorX plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"multivendorx","vendor":"multivendorx"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.4. This is due to missing or incorrect nonce validation on several functions in api/class-mvx-rest-controller.php. This makes it possible for unauthenticated attackers to update vendor account details, create vendor accounts, and delete arbitrary users via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Cross-site request forgery in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2024-9943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"WooCommerce \u003c= 9.0.2 - Unauthenticated HTML Injection","id":"CVE-2024-9944"},"packages":[],"prev":{"headline":"WPGYM \u003c= 67.1.0 - Unauthenticated Arbitrary File Upload","id":"CVE-2024-9942"},"products":["MultiVendorX – WooCommerce Multivendor Marketplace Solutions"],"published":"2024-10-24","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.5,"headline":"WordPress MultiVendorX plugin \u003c= 4.2.22 - Sensitive Data Exposure Vulnerability","id":"CVE-2025-48261","kev_date_added":null,"published":"2025-06-09"},{"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"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wcmp"]},"summary":"Attackers can trick administrators into updating vendor details, creating accounts, or deleting users via forged requests in the MultiVendorX plugin.","url":"https://insights.sbomify.com/CVE-2024-9943/"}