Skip to main content
VulnerabilityPublished

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

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 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
GitHubfffccx1/cmspkg:github/fffccx1/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-46394, organizations should implement robust anti-CSRF protections in FrogCMS, especially on sensitive administrative endpoints like /admin/?/user/add. This includes integrating unique, unpredictable CSRF tokens in all state-changing requests and validating these tokens server-side before processing. Additionally, enforcing strict user session management and limiting administrative access to trusted networks or VPNs can reduce exposure. Administrators should be trained to recognize phishing and social engineering attempts that could trigger CSRF attacks. Monitoring and logging administrative actions can help detect suspicious activities early. If possible, upgrading to a patched version of FrogCMS or applying vendor-provided fixes is recommended once available. As a temporary measure, disabling or restricting access to vulnerable endpoints until a fix is deployed can reduce risk. Employing web application firewalls (WAFs) with CSRF detection rules may also provide an additional layer of defense.

Description

FrogCMS v0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) via /admin/?/user/add

References

Community reviews

Loading reviews…