Skip to main content
VulnerabilityPublished Updated

CVE-2024-42624: cms · Cross-Site Request Forgery (CSRF)

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubkirtoc/cmspkg:github/kirtoc/cmsOther threatsAffected
  • =0.9.5
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-42624, organizations should implement the following specific measures: 1) Immediately restrict administrative access to the FrogCMS backend by IP whitelisting or VPN-only access to reduce exposure. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the /admin/?/page/delete/ endpoint, especially those lacking valid CSRF tokens or originating from untrusted referrers. 3) Educate administrators to avoid clicking on untrusted links or visiting suspicious websites while logged into the CMS to reduce the risk of CSRF exploitation. 4) If possible, implement manual CSRF token validation in the CMS codebase or deploy reverse proxies that inject and validate anti-CSRF tokens. 5) Regularly back up CMS content and configurations to enable rapid recovery from unauthorized deletions. 6) Monitor server and application logs for unusual deletion requests or patterns indicative of CSRF attacks. 7) Engage with FrogCMS developers or community to track patch releases and apply updates promptly once available. These targeted actions go beyond generic advice by focusing on access control, detection, and user behavior to mitigate the specific risks posed by this vulnerability.

Description

FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/page/delete/10.

References

Community reviews

Loading reviews…