CVE-2024-22819: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
AI-suggested
European organizations should immediately implement strict web application firewall (WAF) rules to detect and block suspicious requests targeting the /system/email/email_templets_update endpoint. Employing anti-CSRF tokens in all state-changing requests is critical; if FlyCms does not support this natively, organizations should consider custom development or proxy solutions to enforce it. Restricting access to the email template update functionality to only highly trusted users and limiting session lifetimes can reduce exposure. Network segmentation and monitoring for unusual outbound email patterns can help detect exploitation attempts. User awareness training to avoid clicking on untrusted links while authenticated to FlyCms is also important. Until an official patch is released, organizations should consider disabling or restricting the vulnerable functionality if feasible. Regular backups of email templates should be maintained to enable quick restoration if tampering occurs.
Description
FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/email/email_templets_update.