Skip to main content
CVE-2024-42627VulnerabilityPublished Updated

CVE-2024-42627: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 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 2026-10-26.

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-42627, 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 unavailable, implement web application firewall (WAF) rules to detect and block suspicious requests targeting the snippet deletion endpoint. 3) Enforce strict access controls limiting administrative interface access to trusted IP addresses or VPNs. 4) Require multi-factor authentication (MFA) for all administrative users to reduce the risk of compromised credentials. 5) Implement CSRF tokens in all state-changing requests within FrogCMS to prevent unauthorized actions. 6) Educate administrators to avoid clicking on untrusted links or visiting suspicious websites while logged into the CMS. 7) Regularly back up website content and configuration to enable quick restoration in case of content deletion. 8) Monitor logs for unusual deletion activities or access patterns to detect potential exploitation attempts early. These targeted steps go beyond generic advice and address the specific attack vector and environment of FrogCMS 0.9.5.

Description

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

References

Community reviews

Loading reviews…