dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-30247

CRITICAL · 9.3 CVSS v4.0 Published 2025-09-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An OS command injection vulnerability in user interface in Western Digital My Cloud firmware prior to 5.31.108 on NAS platforms allows remote attackers to execute arbitrary system commands via a specially crafted HTTP POST.

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

OS command injection vulnerability in the web interface of Western Digital My Cloud NAS firmware versions prior to 5.31.108 allows remote attackers to execute arbitrary system commands by sending a specially crafted HTTP POST request to the UI. The CVSS 9.3 score indicates trivial exploitability with complete system compromise potential.

MitigationUpgrade Western Digital My Cloud firmware to version 5.31.108 or later. If immediate patching is not feasible, restrict network access to the device's administrative web interface and monitor for suspicious HTTP POST requests.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm you are running a Western Digital My Cloud NAS device
    Access the device administrative interface or check the device label/model number. The web interface is typically accessible at http://[device-ip]/ or via the My Cloud dashboard.
    Affected if The device is a Western Digital My Cloud NAS series
  2. Check the installed firmware version
    Log into the web UI, navigate to Settings > About or Settings > System > Firmware. Alternatively, access the device via SSH and run: cat /etc/version or cat /mnt/boot/VERSION 2>/dev/null
    Affected if The firmware version is lower than 5.31.108 (e.g., 5.31.107, 5.30.x, etc.)
  3. Verify the administrative web interface is enabled
    Check the device settings to confirm the web UI service is active. Typically found under Settings > Network or Settings > Services. Via CLI: ps aux | grep -i http or systemctl status webserver 2>/dev/null
    Affected if The web interface service is running and accessible on the network
  4. Review HTTP access logs for suspicious POST requests
    If SSH access is available, examine web server logs. Common paths include: /var/log/httpd/access_log, /var/log/lighttpd/access.log, or /var/log/nginx/access.log. Look for unusual POST requests to /api/ endpoints or unexpected command strings.
    Affected if Unexpected POST requests containing shell metacharacters (;, |, &, $(), ``) are present in the logs

You are affected if you are running a Western Digital My Cloud NAS with firmware version below 5.31.108 and the administrative web interface is accessible.

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 Western Digital My Cloud firmware to version 5.31.108 or later. If immediate patching is not feasible, restrict network access to the device's administrative web interface and monitor for suspicious HTTP POST requests.

Recommended fix High confidence

My Cloud firmware 5.31.108 or later

  1. Download My Cloud firmware version 5.31.108 or later from the official Western Digital support website
  2. Access the My Cloud device web interface
  3. Navigate to Settings > Firmware Update or similar firmware management section
  4. Upload and install the firmware version 5.31.108 or later
  5. Verify the firmware update was successful and the device is running the patched version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30247 — 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-30247 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