Skip to main content
CVE-2024-21732VulnerabilityPublished Updated

CVE-2024-21732: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% 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:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 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 2026-10-25.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should first verify if they are using FlyCms and identify affected versions. Since no official patches are currently available, organizations should implement the following measures: 1) Apply strict input validation and output encoding on all user inputs related to the permission management feature to neutralize malicious scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 3) Educate users, especially administrators, about phishing and social engineering risks to reduce the chance of clicking malicious links. 4) Monitor web server and application logs for unusual activity or attempts to inject scripts. 5) If possible, restrict access to the permission management interface to trusted networks or VPNs to limit exposure. 6) Stay alert for official patches or updates from FlyCms developers and apply them promptly once released. 7) Consider implementing web application firewalls (WAF) with rules to detect and block XSS payloads targeting the CMS.

Description

FlyCms through abbaa5a allows XSS via the permission management feature.

References

Community reviews

Loading reviews…