{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30401 is a medium-severity code injection vulnerability in Facebook WhatsApp Desktop for Windows, published on 5 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-30401 and fix it if it is affected.\n\nWhat it is: CVE-2025-30401 is a medium-severity code injection vulnerability in Facebook WhatsApp Desktop for Windows, published on 5 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-30401 in the wild and no public exploit code.\n\nAffected product: Facebook WhatsApp Desktop for Windows. 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-30401/ (Markdown: https://insights.sbomify.com/CVE-2025-30401/index.md)","id":"CVE-2025-30401","markdown":"https://insights.sbomify.com/CVE-2025-30401/index.md","name":"CVE-2025-30401","record":{"aliases":["GHSA-hp4v-q7qc-45wr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp Desktop","requires_auth":"low_privilege","summary":"A spoofing flaw in WhatsApp Desktop for Windows allowed attackers to execute arbitrary code by mismatching MIME types and file extensions.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":6.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[],"description":"A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file opening handler based on the attachment’s filename extension. A maliciously crafted mismatch could have caused the recipient to inadvertently execute arbitrary code rather than view the attachment when manually opening the attachment inside WhatsApp. We have not seen evidence of exploitation in the wild.","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":"Code injection in WhatsApp Desktop for Windows","id":"CVE-2025-30401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"ExecuTorch vulnerable to Heap-based Buffer Overflow attack","id":"CVE-2025-30402"},"packages":[],"prev":{"headline":"Microsoft Windows DWM Core Library Use-After-Free","id":"CVE-2025-30400"},"products":["WhatsApp Desktop for Windows"],"published":"2025-04-05","related":[{"cvss_score":9.8,"headline":"WhatsApp VOIP Stack Buffer Overflow","id":"CVE-2019-3568","kev_date_added":"2022-04-19","published":"2019-05-14"},{"cvss_score":8.2,"headline":"WhatsApp Cross-Site Scripting","id":"CVE-2019-18426","kev_date_added":"2022-05-23","published":"2020-01-21"},{"cvss_score":5.4,"headline":"Meta Platforms WhatsApp Incorrect Authorization","id":"CVE-2025-55177","kev_date_added":"2025-09-02","published":"2025-08-29"},{"cvss_score":9.8,"headline":"Integer overflow in WhatsApp Business for Android","id":"CVE-2022-36934","kev_date_added":null,"published":"2022-09-22"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24042","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24041","kev_date_added":null,"published":"2021-12-07"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24026","kev_date_added":null,"published":"2021-04-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["Facebook"]},"summary":"A spoofing flaw in WhatsApp Desktop for Windows allowed attackers to execute arbitrary code by mismatching MIME types and file extensions.","url":"https://insights.sbomify.com/CVE-2025-30401/"}