Skip to content
Fencer Intel
medium 5.8

CVE-2024-45607 json

whatsapp-api-js fails to validate message's signature

published 2y ago modified 4mo ago also GHSA-mwhf-vhr5-7j23 , EUVD-2024-2839

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
14.5%
EPSS 14.5% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

whatsapp-api-js is a TypeScript server agnostic Whatsapp's Official API framework. It's possible to check the payload validation using the WhatsAppAPI.verifyRequestSignature and expect false when the signature is valid. Incorrect Access Control, anyone using the post or verifyRequestSignature methods to handle messages is impacted. This vulnerability is fixed in 4.0.3.

Patch / fix

  • npm whatsapp-api-js 4.0.3
  • secreto31126 whatsapp-api-js 4.0.3

Is CVE-2024-45607 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

14.47% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm whatsapp-api-js
>=4.0.0, <4.0.3
4.0.3

Affected products

  • Secreto31126 whatsapp-api-js

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.