How severe is CVE-2024-45607?

CVE-2024-45607 has a CVSS score of 5.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-45607?

CVE-2024-45607 affects the following packages: whatsapp-api-js (npm). Ecosystems affected: npm.

How do I fix CVE-2024-45607?

Update whatsapp-api-js to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45607 is resolved across your whole dependency graph.

How do I detect CVE-2024-45607 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for whatsapp-api-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-45607 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2024-45607 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-45607 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-45607?

CVE-2024-45607 has an EPSS (Exploit Prediction Scoring System) score of 14.5%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2024-45607?

CVE-2024-45607 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-45607 published, and has it been updated?

CVE-2024-45607 was published on September 12, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

CVE-2024-45607 — whatsapp-api-js

MEDIUMFix: Secreto31126/whatsapp-api-js@56620c6

CVE-2024-45607 is a medium-severity (CVSS 5.8) CWE-347 vulnerability in whatsapp-api-js. EPSS puts its 30-day exploitation probability at 14.5% (97th percentile). A fix is available for whatsapp-api-js — see the affected versions and patch details below.

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

Also known asGHSA-mwhf-vhr5-7j23

Published

Sep 12, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45607.

EPSS Exploitation Probability

via FIRST.org ↗

14.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

whatsapp-api-jsnpm

7Kdownloads / week

Description

Impact

Incorrect Access Control, anyone using the post or verifyRequestSignature methods to handle messages is impacted.

Patches

Patched in version 4.0.3.

Workarounds

It's possible to check the payload validation using the WhatsAppAPI.verifyRequestSignature and expect false when the signature is valid.

function doPost(payload, header_signature) {
    if (whatsapp.verifyRequestSignature(payload.toString(), header_signature) {
        throw 403;
    }
    
    // Now the payload is correctly verified
    whatsapp.post(payload);
}

References

https://github.com/Secreto31126/whatsapp-api-js/pull/371

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`whatsapp-api-js`	≥ 4.0.0&&< 4.0.3	4.0.3`npm install whatsapp-api-js@4.0.3`

Affected Products

1 product · 1 configurations

Application

whatsapp-api-jssecreto31126

≥ 4.0.0 && < 4.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for whatsapp-api-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update whatsapp-api-js to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45607 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Incorrect Access Control, anyone using the post or verifyRequestSignature methods to handle messages is impacted. ### Patches Patched in version 4.0.3. ### Workarounds It's possible to check the payload validation using the WhatsAppAPI.verifyRequestSignature and expect false when the signature is valid. ```ts function doPost(payload, header_signature) { if (whatsapp.verifyRequestSignature(payload.toString(), header_signature) { throw 403; } // Now the payload is correctly verified whatsapp.post(payload); } ``` ### References https://github.com/Secret