CVE-2024-44721: CMS · Server-Side Request Forgery (SSRF)
Affects CMSSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubseacms-net/CMSpkg:github/seacms-net/CMSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-44721, organizations should immediately implement strict input validation and sanitization on the 'url' parameter in /admin_reslib.php to prevent malicious SSRF payloads. Network-level controls should be enforced to restrict outbound HTTP requests from the CMS server to only trusted destinations, using firewall rules or proxy whitelisting. If a patch becomes available from SeaCMS developers, it should be applied promptly. In the absence of an official patch, consider disabling or restricting access to the vulnerable endpoint for untrusted users. Employ web application firewalls (WAFs) with SSRF detection capabilities to monitor and block suspicious requests. Regularly audit and monitor server logs for unusual outbound requests indicative of SSRF exploitation attempts. Additionally, segment internal networks to limit the impact of potential SSRF attacks and reduce access to sensitive internal services.
Description
SeaCMS v13.1 was discovered to a Server-Side Request Forgery (SSRF) via the url parameter at /admin_reslib.php.