CVE-2025-14693
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 has been found in Ugreen DH2100+ up to 5.3.0. This affects an unknown function of the component USB Handler. Such manipulation leads to symlink following. The attack can be executed directly on the physical device. The exploit has been disclosed to the public and may be used. It is suggested to upgrade the affected component.
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 symlink following vulnerability exists in the USB Handler component of Ugreen DH2100+ NAS devices up to version 5.3.0. An attacker with direct physical access to the device can manipulate symlinks to traverse the file system and access unauthorized files or directories outside intended boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Physical
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:H/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 device modelCheck the NAS device model through the administrative web interface, device label, or system information page. Confirm it is a Ugreen DH2100+ model.Affected if The device is not a Ugreen DH2100+ NAS, then this specific CVE does not apply.
-
Determine the installed firmware versionAccess the device admin panel or system settings to view the current firmware version. Compare this against the affected range of all versions up to and including 5.3.0.Affected if The firmware version is 5.3.0 or lower, indicating the device falls within the affected version range.
-
Verify USB Handler component statusCheck the device configuration to determine if USB support or the USB Handler feature is enabled. This may be visible in storage settings, external device settings, or USB sharing options.Affected if USB Handler is disabled or USB ports are not configured, the attack surface may be reduced but the vulnerable code may still be present in the firmware.
-
Assess physical access exposureEvaluate whether USB ports on the device are physically accessible to unauthorized individuals. Consider device placement, enclosure security, and whether external USB ports are in use.Affected if USB ports are physically accessible to attackers, the prerequisite for exploiting this vulnerability is satisfied.
A defender is affected if they own a Ugreen DH2100+ NAS running firmware version 5.3.0 or lower with USB functionality accessible via physical ports.
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 dataUpgrade the Ugreen DH2100+ firmware to a version newer than 5.3.0 per vendor guidance. Since this requires physical access, enforce physical security controls around the device and audit USB interactions.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14693 — 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-14693 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