CVE-2024-39713 is a high-severity (CVSS 8.6) Server-Side Request Forgery (SSRF) vulnerability in rocket.chat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for rocket.chat — see the affected versions and patch details below.
Rocket.Chat Server-Side Request Forgery (SSRF) vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-39713.
EPSS Exploitation Probability
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
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.
rocket.chatnpmDescription
A Server-Side Request Forgery (SSRF) affects Rocket.Chat's Twilio webhook endpoint before version 6.10.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | rocket.chat | all versions | 6.10.1npm install rocket.chat@6.10.1 |
Affected Products
rocket.chatrocket.chatResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rocket.chat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rocket.chat to 6.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39713 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
How to detect CVE-2024-39713
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-39713 -u https://target- Template
- Rocket.Chat - Server-Side Request Forgery (SSRF)
- Severity
- high
- Impact
- Unauthenticated attackers can force the server to make arbitrary requests, potentially accessing internal services.
- Remediation
- Update Rocket.Chat to version 6.10.1 or later.
Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-39713 in your dependencies?
Find it across npm, including transitive dependencies.