Skip to main content
VulnerabilityPublished Updated

CVE-2024-22592: FlyCms · Cross-Site Request Forgery (CSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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 18 Jan 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

AI-suggested

  1. Immediately implement CSRF protections on the /system/user/group_update endpoint by adding anti-CSRF tokens that are validated on the server side for all state-changing requests.
  2. Enforce strict same-site cookie policies (e.g., SameSite=Lax or Strict) to reduce the risk of CSRF attacks.
  3. Require re-authentication or multi-factor authentication (MFA) for sensitive operations such as user group updates to add an additional security layer.
  4. Monitor web server logs for unusual POST requests to the vulnerable endpoint, especially those originating from external referrers or suspicious user agents.
  5. Educate users about phishing and social engineering risks to reduce the likelihood of user interaction leading to exploitation.
  6. If possible, isolate or restrict access to the FlyCms administrative interface to trusted IP addresses or VPNs.
  7. Engage with the FlyCms vendor or community to obtain or request an official patch or update addressing this vulnerability.
  8. Conduct regular security assessments and penetration testing focused on CSRF and other web vulnerabilities in FlyCms deployments.

Description

FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/user/group_update

References

Community reviews

Loading reviews…