VulnerabilityPublished 21 Aug 2025Updated 22 Aug 2025

CVE-2025-51818: MCCMS · Exposed Files or Directories

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Aug 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

European organizations should prioritize the following mitigation steps: 1) Immediately audit and restrict access controls to the MCCMS Backups.php component to ensure only trusted and necessary users have privileges. 2) Monitor logs for unusual file deletion activities or command execution attempts related to the backup system. 3) Implement network segmentation to limit exposure of MCCMS servers to untrusted networks or users. 4) Develop and enforce strict backup retention policies, including offsite and immutable backups, to mitigate the impact of any deletion. 5) Engage with the MCCMS vendor or community to obtain patches or updates addressing CVE-2025-51818 as soon as they become available. 6) Conduct penetration testing focused on backup management components to identify and remediate similar weaknesses. 7) Employ application-level whitelisting or file integrity monitoring to detect unauthorized file deletions or modifications. These targeted actions go beyond generic advice by focusing on access control, monitoring, and backup resilience specific to the vulnerable component.

Description

MCCMS 2.7.0 is vulnerable to Arbitrary file deletion in the Backups.php component. This allows an attacker to execute arbitrary commands

Impact

For European organizations using MCCMS 2.7.0, this vulnerability poses a risk primarily to the integrity and confidentiality of their systems. The ability to delete arbitrary files in the backup management module can result in loss of critical backup data, severely impacting disaster recovery and business continuity plans. Additionally, the potential for arbitrary command execution could allow attackers to escalate privileges or move laterally within the network, increasing the risk of data breaches or system compromise. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, could face regulatory and reputational consequences if backups are compromised or if attackers leverage this vulnerability to access sensitive data. The medium severity rating suggests that while the vulnerability is not trivial, it requires some level of access, which may limit exposure to external attackers but remains a significant threat from insider threats or attackers who have already gained limited access.

CWE-552Files or Directories Accessible to External Parties (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.1 (opens in a new tab)
V12.4.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
Attack patterns
Collect Data from Common Resource Locations (opens in a new tab)
Probe System Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Aug 2025, 01:10 UTC

WeaknessesCWE-552

Technical details

References

Community reviews

Related threats