Skip to main content
CVE-2024-42631VulnerabilityPublished Updated

CVE-2024-42631: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

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

Organizations should immediately implement the following mitigations: 1) Restrict access to the /admin interface by IP whitelisting or VPN to limit exposure to trusted users only. 2) Employ anti-CSRF tokens in all state-changing requests within FrogCMS, if possible by custom patching or configuration. 3) Educate administrators to avoid clicking on suspicious links or visiting untrusted websites while logged into the CMS. 4) Monitor administrative logs for unusual or unauthorized changes to layouts or configurations. 5) If feasible, isolate the CMS environment and apply web application firewalls (WAFs) with rules to detect and block CSRF attack patterns. 6) Regularly check for official patches or updates from FrogCMS and apply them promptly once available. 7) Consider migrating to alternative CMS platforms with active security support if FrogCMS updates are not forthcoming. These steps go beyond generic advice by focusing on access control, user behavior, and proactive monitoring tailored to this specific vulnerability.

Description

FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/layout/edit/1.

References

Community reviews

Loading reviews…