NVD / CVE Program· CNA facebook

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

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 20.9% (FIRST EPSS); higher than 97.5% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Facebook WhatsApp Desktop for Windows 2.2450.6.

Low priority for now. Upgrade to Facebook WhatsApp Desktop for Windows 2.2450.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.7 · v3.1—No exploit Fix available

BDU:2025-04971

Published: Apr 5, 2025
Updated: Jun 17, 2026
EPSS: 20.9% · 97th percentile
CWE: CWE-430

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 6 / 30 · 20.9%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
whatsapp	whatsapp	cpe:2.3:a:whatsapp:whatsapp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

whatsapp whatsappbefore 2.2450.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (facebook). Independent of NVD's CPE analysis and usually ahead of it.

Facebook WhatsApp Desktop for Windows
- 0.0.0 and later · before 2.2450.6affected · semver

Same product

whatsapp: all records

Other highest-scoring records for the same primary product.

CVE-2019-18426A vulnerability in WhatsApp Desktop versions prior to 0.3.9309 when paired with WhatsApp for iPhone versions prior to 2.20.10 allows cross-sKEV
82Now
CVE-2019-3568A buffer overflow vulnerability in WhatsApp VOIP stack allowed remote code execution via specially crafted series of RTCP packets sent to a KEV
78This week
CVE-2025-55177Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25KEV
55Plan

Published before and after this one in the same product

← EarlierCVE-2023-38537Oct 4, 2023 · A race condition in a network transport subsystem led to a heap use-after-free issue in established or unsilenced incoming audio/video calls
22Monitor
← EarlierCVE-2023-38538Oct 4, 2023 · A race condition in an event subsystem led to a heap use-after-free issue in established audio/video calls that could have resulted in app t
20Monitor
Later →CVE-2025-55179Nov 18, 2025 · Incomplete validation of rich response messages in WhatsApp for iOS prior to v2.25.23.73, WhatsApp Business for iOS v2.25.23.82, and WhatsAp
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Facebook WhatsApp Desktop for Windows	2.2450.6	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).