CVE-2025-14224
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in the File Upload component of Yottamaster DM2, DM3, and DM200 NAS devices (versions up to 1.2.23/1.9.12) allows remote attackers to write files to arbitrary locations on the device filesystem by manipulating file path sequences during upload operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.9.12<= 1.9.12<= 1.2.23CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Yottamaster NAS modelAccess the device admin interface or check the device label to confirm the exact model number (DM2, DM3, or DM200)Affected if The device is not one of these three models - this CVE only applies to DM2, DM3, and DM200
-
Check the installed firmware versionLog into the device admin panel and navigate to System Settings > Firmware/About page, or use the command line (if accessible) to run: cat /etc/version or check the web interface version displayAffected if The firmware version is 1.9.12 or lower for DM2/DM3, or 1.2.23 or lower for DM200
-
Verify if the File Upload component is enabledIn the admin interface, navigate to the File Sharing or Upload settings section to confirm whether the upload functionality is activeAffected if The File Upload feature is enabled and accessible to users or attackers
-
Inspect the filesystem for unexpected files in system directoriesCheck common directories such as /, /www, /var/www, /tmp, /mnt, and /home for newly created or unfamiliar files, especially executable scripts, shells, or configuration files that were not part of the original firmwareAffected if Files exist in system directories outside of expected upload paths, or unusual scripts are present in web-accessible folders
-
Review access logs for anomalous upload requestsExamine web server logs (typically in /var/log or accessible via the admin panel) for upload requests containing path traversal sequences like ../, ..\, or absolute paths such as /etc/passwdAffected if Upload requests contain path traversal patterns or attempt to write files outside the designated upload directory
You are affected if you own a DM2, DM3, or DM200 device running firmware at or below the affected version thresholds AND the File Upload feature is enabled, regardless of network exposure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond to early disclosure, implement network segmentation to limit exposure, restrict the upload functionality via firewall rules or access controls, and monitor for indicators of compromise until an official firmware patch becomes available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data