Skip to main content
VulnerabilityPublished Updated

CVE-2024-22699: 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, 11:07 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 28% 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

To mitigate this vulnerability, European organizations should first identify all instances of FlyCms v1.0 in their environment. Since no official patches are currently available, organizations should implement compensating controls immediately. These include enforcing strict anti-CSRF tokens on all state-changing requests, especially on the /system/admin/update_group_save endpoint. Web Application Firewalls (WAFs) should be configured to detect and block suspicious CSRF patterns or anomalous requests targeting administrative endpoints. Organizations should also enhance user awareness training to reduce the risk of social engineering attacks that could trigger CSRF exploits. Network segmentation and strict access controls limiting administrative interface exposure to trusted networks or VPNs can reduce attack surface. Monitoring and logging of administrative actions should be intensified to detect unauthorized changes promptly. Once a vendor patch is released, organizations must prioritize timely deployment. Additionally, conducting regular security assessments and penetration testing focused on CSRF and related vulnerabilities will help identify and remediate similar issues proactively.

Description

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

References

Community reviews

Loading reviews…