dbcve.org
InjectionWeakness · CWE-74

CVE-2025-14188

HIGH · 7.2 CVSS v3.1 Published 2025-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A security vulnerability has been detected in UGREEN DH2100+ up to 5.3.0.251125. This impacts the function handler_file_backup_create of the file /v1/file/backup/create of the component nas_svr. The manipulation of the argument path leads to command injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. Upgrading the affected component is advised.

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 confidence

Command injection vulnerability in UGREEN DH2100+ NAS devices allows remote attackers to execute arbitrary commands via manipulation of the 'path' argument in the /v1/file/backup/create endpoint (function handler_file_backup_create) in the nas_svr component.

MitigationUpgrade the UGREEN DH2100+ firmware to a version beyond 5.3.0.251125 to address the command injection vulnerability in the backup creation functionality.

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NAS device model
    Check the device model label on the physical device or access the NAS web interface to view system information. Look for 'DH2100+' in the model name.
    Affected if The device is not a UGREEN DH2100+ NAS, the vulnerability does not apply.
  2. Check the installed firmware version
    Access the NAS web interface, navigate to System Settings > System Update or About, and record the firmware version number displayed.
    Affected if The firmware version is 5.3.0.251125 or earlier; versions prior to the fix are considered affected.
  3. Verify the nas_svr component is running
    Access the NAS via SSH or telnet if enabled, then run 'ps | grep nas_svr' or check the process list for the nas_svr daemon.
    Affected if The nas_svr component is not present or not running, the specific endpoint may not be functional.
  4. Confirm backup creation API endpoint exists
    Inspect network traffic or check the API documentation for the device to confirm the /v1/file/backup/create endpoint exists in the nas_svr component.
    Affected if The endpoint is not present in the installed version, the command injection vector does not exist.

The environment is affected if the device is a UGREEN DH2100+ NAS running firmware version 5.3.0.251125 or earlier, with the nas_svr component active and the backup creation API endpoint available.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the UGREEN DH2100+ firmware to a version beyond 5.3.0.251125 to address the command injection vulnerability in the backup creation functionality.

Recommended fix Moderate confidence

Any firmware version newer than 5.3.0.251125 (e.g., latest DH2100+ firmware released by UGREEN)

  1. Log in to the UGREEN DH2100+ web interface and note the current firmware version under System Settings > Firmware/Upgrade.
  2. Visit the official UGREEN support or download page and locate the most recent firmware release for the DH2100+ (any version newer than 5.3.0.251125).
  3. Backup the device configuration via the admin panel to preserve settings.
  4. Upload and apply the new firmware using the device’s firmware upgrade function.
  5. After the device restarts, verify the new firmware version is displayed in the web UI.
  6. Confirm the vulnerability is remediated by attempting to access the /v1/file/backup/create endpoint with a test payload (e.g., using curl) – the request should be rejected or the service should respond with an error.
Caveat Firmware updates may reset certain settings; ensure you have a configuration backup and review release notes for any breaking changes.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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