VulnerabilityPublished 19 Sep 2025

CVE-2025-55910: CMSEasy · Incomplete Cleanup

Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% 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:L/I:L/A:L

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Sep 2025
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

AI-suggested

Given the lack of an official patch, European organizations should immediately audit their CMSEasy installations to identify affected versions (7.7.8.0 and earlier). Restrict access to the database_admin.php script by implementing strict access controls such as IP whitelisting, VPN-only access, or multi-factor authentication to limit exposure. Employ web application firewalls (WAFs) with rules designed to detect and block suspicious file deletion attempts targeting this script. Regularly back up website files and databases to enable rapid recovery in case of file deletion. Monitor logs for unusual activity related to file operations or access to administrative scripts. If possible, isolate the CMS environment from other critical systems to contain potential damage. Engage with CMSEasy vendors or community forums to track patch releases and apply updates promptly once available. Finally, conduct security awareness training for administrators to recognize and report suspicious behavior.

Description

CMSEasy v7.7.8.0 and before is vulnerable to Arbitrary file deletion in database_admin.php.

Impact

For European organizations using CMSEasy, this vulnerability could have serious consequences. Arbitrary file deletion can disrupt business-critical websites and services, leading to downtime and loss of customer trust. It may also result in data loss or corruption, impacting data integrity and compliance with regulations such as GDPR. Organizations in sectors relying heavily on web presence, including e-commerce, media, and government services, could face operational interruptions. Additionally, if exploited by threat actors, it could serve as a foothold for further attacks, including ransomware or data breaches. The impact is heightened in Europe due to stringent data protection laws and the reputational damage associated with service outages or data loss. The absence of known exploits currently provides a window for mitigation before active exploitation occurs.

CWE-459Incomplete Cleanup (opens in a new tab)
Base weakness
The product does not properly "clean up" and remove temporary or supporting resources after they have been used.
Architecture and Design · Implementation
Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/Y4y17/CVE/blob/main/CMSEasy/Arbitrary%20file%20deletion%20vulnerability.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 19 Sep 2025, 15:52 UTC

WeaknessesCWE-459

Technical details

References

Community reviews

Related threats