Skip to main content
VulnerabilityPublished Updated

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

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% 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 2 Feb 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
GitHubharryrabbit5651/cmspkg:github/harryrabbit5651/cmsOther threatsAffected
  • =2.33
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-24524, organizations should immediately implement CSRF protections such as synchronizer tokens or double-submit cookies in the flusity-CMS environment, especially around the add_menu.php component. Restrict access to the add_menu.php script by IP whitelisting or network segmentation to limit exposure. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts targeting the vulnerable endpoint. Educate users to avoid clicking on untrusted links or performing sensitive actions without verifying the source. Monitor web server logs and application logs for unusual POST requests or patterns indicative of CSRF exploitation attempts. If possible, disable or restrict the add_menu.php functionality until a vendor patch is available. Regularly check for updates from the flusity-CMS vendor and apply patches promptly once released. Conduct security assessments and penetration testing focused on CSRF and related vulnerabilities in the CMS environment. Implement multi-factor authentication (MFA) to reduce the risk of session hijacking that could facilitate exploitation.

Description

Cross Site Request Forgery (CSRF) vulnerability in flusity-CMS v.2.33, allows remote attackers to execute arbitrary code via the add_menu.php component.

References

Community reviews

Loading reviews…