Skip to main content
VulnerabilityPublished Updated

CVE-2024-25502: flusity-CMS · Directory Traversal

Affects flusity-CMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Feb 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
GitHubflusity/flusity-CMSpkg:github/flusity/flusity-CMSOther threatsAffected
  • =2.4
Fixed in–

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

AI-suggested

To mitigate CVE-2024-25502, organizations should immediately restrict access to the download_backup.php component by limiting it to trusted IP addresses or internal networks using firewall rules or web server access controls. Deploying a web application firewall (WAF) with custom rules to detect and block directory traversal patterns and suspicious requests targeting backup download functionality can reduce exposure. Until an official patch is released, consider disabling or removing the download_backup.php script if backup downloads are not urgently needed. Conduct thorough input validation and sanitization on any user-supplied parameters related to file paths to prevent traversal attacks. Regularly monitor web server logs and intrusion detection systems for anomalous access attempts or exploitation indicators. Organizations should also maintain offline backups and prepare incident response plans to quickly contain and remediate any compromise. Engage with the Flusity CMS vendor or community to obtain patches or updates as soon as they become available and apply them promptly.

Description

Directory Traversal vulnerability in flusity CMS v.2.4 allows a remote attacker to execute arbitrary code and obtain sensitive information via the download_backup.php component.

References

Community reviews

Loading reviews…