CVE-2024-42632: 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.3% chance of exploitation in 30 days – higher than 25% 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 CSRF vulnerability in FrogCMS 0.9.5, organizations should implement the following specific measures: 1) Apply any official patches or updates from FrogCMS as soon as they become available. 2) If patches are not yet released, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests to the /admin/?/page/add endpoint, especially those lacking valid CSRF tokens or originating from untrusted sources. 3) Enforce strict same-site cookie attributes (SameSite=Lax or Strict) to reduce the risk of cross-origin requests. 4) Implement or verify the presence of anti-CSRF tokens in all state-changing forms and validate these tokens server-side. 5) Restrict administrative access to trusted IP ranges or VPNs to reduce exposure. 6) Educate administrators about the risks of clicking on untrusted links while logged into the CMS. 7) Monitor logs for unusual administrative activity or requests to the vulnerable endpoint. 8) Consider temporary disabling of the vulnerable functionality if feasible until a patch is applied. These targeted actions go beyond generic advice by focusing on the specific vulnerable endpoint and the nature of the CSRF attack vector.
Description
FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/page/add.