CVE-2024-55086: GetSimple CMS CE · Server-Side Request Forgery (SSRF)
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 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
To mitigate CVE-2024-55086, organizations should first verify if they are running GetSimple CMS CE version 3.3.19 or any version affected by this SSRF vulnerability. Implementing firewall rules to block outbound requests from the CMS server to internal IP ranges can reduce SSRF exploitation risk. Monitoring and logging all outbound HTTP requests from the CMS server can help detect suspicious activity. Additionally, applying the principle of least privilege to backend users reduces the risk of exploitation by compromised accounts. Organizations should stay alert for official patches or updates from GetSimple CMS and apply them promptly once released. Conducting regular security assessments and penetration testing focusing on SSRF and related vulnerabilities is also recommended.
Description
In the GetSimple CMS CE 3.3.19 management page, Server-Side Request Forgery (SSRF) can be achieved in the plug-in download address in the backend management system.