VulnerabilityPublished 26 Feb 2024Updated 28 Aug 2024

CVE-2024-25410: flusity-CMS · Unrestricted File Upload

Affects flusity-CMSSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% 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:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Feb 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubflusity/flusity-CMS`pkg:github/flusity/flusity-CMS`Other threats	Affected =2.33	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-25410, organizations should implement the following specific measures: 1) Immediately restrict file upload functionality in update_setting.php to only allow safe, expected file types using strict server-side validation and whitelist approaches. 2) Implement robust content-type and file extension checks, and verify file contents (e.g., magic bytes) to prevent disguised malicious files. 3) Employ file upload size limits and scan uploaded files with antivirus or malware detection tools before processing. 4) Isolate uploaded files in non-executable directories and disable script execution permissions on upload folders to prevent execution of malicious code. 5) Monitor web server logs and application logs for unusual upload attempts or suspicious file names. 6) If possible, apply web application firewall (WAF) rules to detect and block malicious upload patterns targeting update_setting.php. 7) Keep the CMS and all related components updated and monitor vendor advisories for official patches or updates. 8) Conduct regular security assessments and penetration testing focused on file upload functionalities. These measures go beyond generic advice by focusing on the specific vulnerable component and practical controls to reduce exploitation risk.

Description

flusity-CMS 2.33 is vulnerable to Unrestricted Upload of File with Dangerous Type in update_setting.php.

Impact

The primary impact of CVE-2024-25410 is on the integrity of affected systems. Successful exploitation allows attackers to upload malicious files, which can lead to remote code execution, website defacement, or unauthorized modification of content and settings within the CMS. This can undermine trust in the affected websites, cause reputational damage, and potentially serve as a foothold for deeper network penetration. Since the vulnerability does not require authentication, any attacker with network access to the update_setting.php endpoint can attempt exploitation, increasing the attack surface. Although confidentiality and availability are not directly impacted, the integrity compromise can indirectly affect availability if attackers deploy disruptive payloads or backdoors. Organizations relying on flusity-CMS 2.33 for their web presence or internal applications face risks of data tampering and unauthorized access, which can have regulatory and operational consequences. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability remains a significant threat if weaponized.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 09:44 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats