CVE-2024-42626: cms · Cross-Site Request Forgery (CSRF)
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 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 |
|---|---|---|
GitHubkirtoc/cmspkg:github/kirtoc/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 this vulnerability effectively, organizations should implement the following specific measures: 1) Apply any available patches or updates from FrogCMS as soon as they are released. 2) If patches are not yet available, implement CSRF protection mechanisms such as synchronizer tokens or double-submit cookies on the /admin/?/snippet/add endpoint to validate the legitimacy of requests. 3) Restrict access to the administrative interface by IP whitelisting or VPN-only access to reduce exposure to external attackers. 4) Educate administrators to avoid clicking on suspicious links or visiting untrusted websites while logged into the CMS. 5) Monitor web server and application logs for unusual POST requests to the snippet addition endpoint and investigate anomalies promptly. 6) Consider implementing Web Application Firewalls (WAFs) with custom rules to detect and block CSRF attack patterns targeting the admin interface. 7) Regularly back up CMS content and configurations to enable rapid recovery in case of compromise. These targeted actions go beyond generic advice by focusing on the specific vulnerable endpoint and the administrative context of the vulnerability.
Description
FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/snippet/add.