CVE-2025-14224VulnerabilityPublished 8 Dec 2025

CVE-2025-14224: Yottamaster DM2 · Path Traversal

Affects Yottamaster DM2Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 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 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 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

Affected software

Product	Affected	Fixed in
Yottamaster DM2	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3 =1.2.4 =1.2.5 =1.2.6 =1.2.7 =1.2.8 =1.2.9 =1.2.10 =1.2.11 =1.2.12 =1.2.13 =1.2.14 =1.2.15 =1.2.16 =1.2.17 =1.2.18 =1.2.19 =1.2.20 =1.2.21 =1.2.22 =1.2.23 =1.9.0 =1.9.1 =1.9.2 =1.9.3 =1.9.4 =1.9.5 =1.9.6 =1.9.7 =1.9.8 =1.9.9 =1.9.10 =1.9.11 =1.9.12	Fixed in–

AI-suggested

European organizations should immediately inventory their environments to identify any Yottamaster DM2, DM3, or DM200 devices running affected versions. Since no official patches are available, organizations must implement compensating controls such as network segmentation to isolate these devices from untrusted networks and restrict access to trusted administrators only. Employ strict firewall rules to limit inbound connections to the minimum necessary and monitor network traffic for anomalous file upload or directory traversal attempts. Implement host-based intrusion detection systems (HIDS) to detect unauthorized file system access or modifications. Regularly back up critical data stored on these devices and verify backup integrity to enable recovery in case of compromise. Consider disabling or restricting file upload functionality if feasible until patches are released. Engage with Yottamaster support channels for updates and apply patches promptly once available. Additionally, conduct security awareness training for administrators managing these devices to recognize exploitation signs and respond swiftly.

Description

A vulnerability was found in Yottamaster DM2, DM3 and DM200 up to 1.2.23/1.9.12. Affected by this issue is some unknown functionality of the component File Upload. Performing manipulation results in path traversal. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of CVE-2025-14224 could be significant depending on the deployment scale of Yottamaster DM2, DM3, and DM200 devices. Organizations relying on these devices for data storage or backup could face unauthorized disclosure of sensitive information or data tampering through file overwrites. This could lead to operational disruptions, data breaches, and compliance violations under GDPR due to unauthorized access to personal data. Critical infrastructure sectors such as finance, healthcare, and government agencies using these devices may experience increased risk of targeted attacks exploiting this vulnerability. The remote exploitability without user interaction or authentication lowers the barrier for attackers, increasing the likelihood of exploitation especially in poorly segmented or exposed network environments. The absence of vendor patches further exacerbates the risk, forcing organizations to rely on compensating controls. Overall, the vulnerability could undermine data integrity and confidentiality, potentially leading to financial loss, reputational damage, and regulatory penalties.

References

Community reviews

Loading reviews…