Skip to main content
VulnerabilityPublished Updated

CVE-2024-27757: flusity-CMS · Cross-site Scripting

Affects flusity-CMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 17:16 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 35% 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 18 Mar 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

Affected software

ProductAffectedFixed in
GitHubjubilianite/flusity-CMSpkg:github/jubilianite/flusity-CMSOther threatsAffected
  • <=2.45
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the cessation of flusity CMS development, organizations should prioritize migration to actively maintained and secure CMS platforms. In the interim, specific mitigations include: 1) Implementing strict input validation and output encoding on the Gallery Name parameter to neutralize malicious scripts. 2) Deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the vulnerable endpoint. 3) Enforcing Content Security Policy (CSP) headers to restrict script execution sources and reduce the impact of injected scripts. 4) Educating users and administrators about phishing and social engineering risks to reduce successful exploitation via user interaction. 5) Monitoring web server logs and application behavior for suspicious requests or anomalies related to the vulnerable parameter. 6) If possible, disabling or restricting access to the vulnerable tools/addons_model.php functionality to limit exposure. These targeted actions can reduce risk while planning for long-term remediation through platform replacement.

Description

flusity CMS through 2.45 allows tools/addons_model.php Gallery Name XSS. The reporter indicates that this product "ceased its development as of February 2024."

References

Community reviews

Loading reviews…