Skip to main content
CVE-2024-42630VulnerabilityPublished Updated

CVE-2024-42630: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 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-25.

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-42630, organizations should implement the following specific measures: 1) Apply any available patches or updates from FrogCMS developers as soon as they are released. 2) If patches are not yet available, implement manual CSRF protections by adding anti-CSRF tokens to all state-changing requests, especially the file creation endpoint. 3) Restrict administrative access to trusted IP addresses or VPNs to reduce exposure. 4) Employ web application firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting the vulnerable endpoint. 5) Educate administrators about phishing risks and encourage cautious behavior regarding unsolicited links or emails. 6) Monitor server logs and application behavior for unusual file creation activities or anomalies. 7) Consider isolating the CMS environment or using containerization to limit potential damage from exploitation. These targeted actions go beyond generic advice and address the specific attack vector and environment.

Description

FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/plugin/file_manager/create_file.

References

Community reviews

Loading reviews…