CVE-2024-51408: Server-Side Request Forgery (SSRF)
Source CVE Database V5
Not known to be exploited · CVSS 8.5 High · fixed in 1.46 : patch affected systems soon.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.46
CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
1. Upgrade AppSmith Community to version 1.46 or later, where this SSRF vulnerability is fixed. 2. If immediate upgrade is not possible, implement network-level restrictions to block outbound HTTP requests from AppSmith servers to the 169.254.169.254 metadata IP address. 3. Use AWS IAM roles with the least privilege principle to limit the scope of credentials accessible via the metadata service. 4. Employ AWS Instance Metadata Service Version 2 (IMDSv2), which requires session tokens and reduces SSRF risks. 5. Monitor application logs and network traffic for unusual requests targeting internal IPs or metadata endpoints. 6. Conduct regular security assessments and penetration tests focusing on SSRF and cloud metadata exposure. 7. Educate developers and administrators about SSRF risks and secure coding practices when handling user-supplied URLs or JSON inputs. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SSRF attempts targeting internal IP ranges.
Description
AppSmith Community 1.8.3 before 1.46 allows SSRF via New DataSource for application/json requests to 169.254.169.254 to retrieve AWS metadata credentials.