Skip to main content
VulnerabilityPublished Updated

CVE-2024-22818: 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, 15:59 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 24% 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

Since no official patches are currently available, European organizations should implement immediate compensating controls to mitigate this CSRF vulnerability. These include: 1) Implementing strict Content Security Policy (CSP) headers to reduce the risk of malicious content injection. 2) Employing anti-CSRF tokens in all state-changing requests, especially on the /system/site/filterKeyword_save endpoint, to ensure requests are legitimate. 3) Restricting HTTP methods to only those necessary (e.g., disallowing GET for state-changing operations). 4) Enforcing SameSite cookie attributes (preferably 'Strict' or 'Lax') to limit cookie transmission in cross-site requests. 5) Educating users about phishing risks and encouraging cautious behavior when clicking links or opening emails. 6) Monitoring web server logs for unusual POST requests to the affected endpoint to detect potential exploitation attempts. 7) If possible, temporarily disabling or restricting access to the vulnerable endpoint until a patch is available. 8) Employing Web Application Firewalls (WAF) with custom rules to detect and block suspicious CSRF attempts targeting this endpoint.

Description

FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerbility via /system/site/filterKeyword_save

References

Community reviews

Loading reviews…