Skip to main content
CVE-2024-42628VulnerabilityPublished Updated

CVE-2024-42628: 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

Until an official patch is released, organizations should implement strict mitigations to reduce risk. These include enforcing multi-factor authentication for administrative access to reduce the risk of compromised credentials being exploited. Administrators should be trained to avoid clicking on suspicious links or visiting untrusted websites while logged into the CMS. Implementing web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests to the snippet editing endpoint can help mitigate exploitation attempts. Additionally, administrators can restrict access to the /admin/ interface by IP whitelisting or VPN-only access to limit exposure. Reviewing and applying HTTP security headers such as SameSite=strict on session cookies can reduce CSRF risks. Monitoring logs for unusual administrative activity and preparing incident response plans are recommended. Once patches become available, prompt application is critical.

Description

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

References

Community reviews

Loading reviews…