dbcve.org
WhatsappApplication

CVE-2025-30401

MEDIUM · 6.7 CVSS v3.1 Published 2025-04-05
Fix available
A fix is available. Upgrade to 2.2450.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a MIME type/extension mismatch spoofing vulnerability in WhatsApp for Windows. The application displays attachments based on their MIME type (the file's internal content type declaration) but selects the handler to open the file based on the filename extension. An attacker could craft a malicious file with a safe-looking MIME type (e.g., application/pdf) but a dangerous extension (e.g., .exe or .scr), causing arbitrary code execution when the user manually opens the attachment within WhatsApp.

MitigationUpdate WhatsApp for Windows to version 2.2450.6 or later. Additionally, organizations should verify that endpoint detection and monitoring are enabled, as this vulnerability could result in code execution even with the patch applied if users open maliciously crafted files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WhatsappApplication
Affected:< 2.2450.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WhatsApp for Windows is installed
    Open Windows Settings > Apps > Installed apps and search for 'WhatsApp', or check the Start Menu for the WhatsApp for Windows application.
    Affected if WhatsApp for Windows is present on the system.
  2. Check installed WhatsApp version
    Open WhatsApp for Windows, click the three-dot menu (top-left), select Help, then select About WhatsApp. Note the version number displayed.
    Affected if The displayed version number is less than 2.2450.6.
  3. Alternatively check version via Windows Settings
    In Windows Settings > Apps > Installed apps, locate WhatsApp for Windows and view its version property under the app details.
    Affected if The listed version is less than 2.2450.6.

A user is affected if WhatsApp for Windows is installed with a version lower than 2.2450.6, as this version range contains the MIME type/extension mismatch vulnerability that could allow arbitrary code execution when opening a maliciously crafted attachment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2450.6 or later
Fixed in 2.2450.6
Interim mitigation

Update WhatsApp for Windows to version 2.2450.6 or later. Additionally, organizations should verify that endpoint detection and monitoring are enabled, as this vulnerability could result in code execution even with the patch applied if users open maliciously crafted files.

Recommended fix High confidence

WhatsApp for Windows version 2.2450.6 or later

  1. Open WhatsApp for Windows
  2. Click on the three-dot menu icon in the top-left corner
  3. Select 'Settings' from the dropdown menu
  4. Navigate to the 'Help' section
  5. Click on 'Check for updates' or 'About' to view current version
  6. If an update is available, click 'Update Now' to download and install version 2.2450.6
  7. Alternatively, download the latest WhatsApp for Windows installer from the official website at www.whatsapp.com
  8. Run the installer and complete the installation
Caveat WhatsApp desktop updates are typically seamless with no breaking changes; chat history and settings are preserved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Whatsapp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data