CyberSecBulletin
CVE-2025-55177Exploited in the wildNVD status: Analyzed

Meta Platforms WhatsApp Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2025-55177 is a medium-severity incorrect authorization vulnerability in WhatsApp Desktop for Mac from Facebook, with a CVSS 3.1 base score of 5.4 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.25.21.78 as the first without the flaw, so updating WhatsApp Desktop for Mac to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 2, 2025, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update WhatsApp Desktop for Mac to 2.25.21.78 or a later version.
  2. Update WhatsApp Business for iOS to 2.25.21.78 or a later version.
  3. Update WhatsApp for iOS to 2.25.21.73 or a later version.
  4. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  5. Read the advisory on facebook.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
FacebookWhatsApp Desktop for Mac2.22.25.2 up to, but not including, 2.25.21.782.25.21.78
FacebookWhatsApp Business for iOS2.22.25.2 up to, but not including, 2.25.21.782.25.21.78
FacebookWhatsApp for iOS2.22.25.2 up to, but not including, 2.25.21.732.25.21.73
WhatsappWhatsapp2.22.25.2 up to, but not including, 2.25.21.73; 2.22.25.2 up to, but not including, 2.25.21.782.25.21.73, 2.25.21.78
WhatsappWhatsapp Business2.22.25.2 up to, but not including, 2.25.21.782.25.21.78

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
LowSome restricted data can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. Scored by CNA (fb.com).

Official description

Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 could have allowed an unrelated user to trigger processing of content from an arbitrary URL on a target’s device. We assess that this vulnerability, in combination with an OS-level vulnerability on Apple platforms (CVE-2025-43300), may have been exploited in a sophisticated attack against specific targeted users.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.