CVE-2025-61318VulnerabilityPublished 8 Dec 2025

CVE-2025-61318: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: 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: 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: None: There is no loss of confidentiality within 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 8 Dec 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 2026-10-26.

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 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

1. Immediately audit all Emlog Pro installations to identify affected versions, specifically version 2.5.20. 2. Apply any official patches or updates released by Emlog Pro developers as soon as they become available. 3. In the absence of patches, implement strict input validation and sanitization on all file deletion parameters, ensuring path traversal sequences (e.g., ../) are blocked. 4. Restrict file system permissions for the web server user to limit the directories and files that can be deleted, ideally confining deletion capabilities to specific safe directories. 5. Monitor web server logs and application logs for suspicious deletion requests or unusual activity patterns. 6. Employ web application firewalls (WAFs) with rules to detect and block directory traversal attempts targeting admin/template.php and admin/plugin.php endpoints. 7. Conduct regular backups of website files and configurations to enable rapid restoration in case of file deletion. 8. Educate administrators on the risks of arbitrary file deletion vulnerabilities and the importance of secure coding and configuration management. 9. Consider isolating the Emlog Pro administrative interface behind VPN or IP allowlists to reduce exposure. 10. Engage in proactive threat hunting to detect any exploitation attempts early.

Description

Emlog Pro 2.5.20 has an arbitrary file deletion vulnerability. This vulnerability stems from the admin/template.php component and the admin/plugin.php component. They fail to perform path verification and dangerous code filtering for deletion parameters, allowing attackers to exploit this feature for directory traversal.

Impact

For European organizations using Emlog Pro 2.5.20, this vulnerability poses a significant risk of unauthorized file deletion, which can lead to service disruption, data loss, and potential compromise of website integrity. Organizations relying on Emlog Pro for public-facing websites or internal content management may experience downtime or defacement if critical files are deleted. The arbitrary file deletion could also be leveraged as a stepping stone for further attacks, such as deleting security logs or configuration files, thereby hindering incident response efforts. The lack of authentication requirement increases the threat surface, allowing attackers to exploit the vulnerability remotely without credentials. This is particularly concerning for European SMEs and public sector entities that may use Emlog Pro due to its ease of use and open-source nature. The impact extends to reputational damage and potential regulatory consequences under GDPR if personal data is affected or service availability is compromised. Given the critical nature of web presence for business continuity, this vulnerability could have wide-reaching operational and financial impacts.

CWE-24Path Traversal: '../filedir' (opens in a new tab)
Variant weakness
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/AndyNull/em/blob/main/emlog%20pro%20-%20del%20vuln.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Dec 2025, 15:41 UTC

WeaknessesCWE-24

Technical details

References

Community reviews

Related threats