dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2023-22816

HIGH · 8.8 CVSS v3.1 Published 2023-06-30
Fix available
A fix is available. Upgrade to 5.26.300 or later.
See remediation →
94/100
Remediation priority · Urgent
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 post-authentication remote command injection vulnerability in a CGI file in Western Digital My Cloud OS 5 devices that could allow an attacker to build files with redirects and execute larger payloads. This issue affects My Cloud OS 5 devices: before 5.26.300.

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 · moderate confidence

A post-authentication remote command injection vulnerability in a CGI file in Western Digital My Cloud OS 5 devices allows authenticated attackers to build files with redirects and execute larger payloads. This RCE exists in the CGI component and can be exploited after successful authentication to the device.

MitigationUpgrade Western Digital My Cloud OS 5 devices to firmware version 5.26.300 or later to remediate this vulnerability.

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
My Cloud OsOperating system
Affected:< 5.26.300

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

CVSS:3.1/AV:N/AC:L/PR:L/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 device model
    Access the device admin web interface or check the device label to confirm it is a Western Digital My Cloud OS 5 device. If the device runs My Cloud OS 5 (not the older My Cloud interface), proceed to version check.
    Affected if The device is a Western Digital My Cloud OS 5 model
  2. Check the installed firmware version
    Log into the My Cloud OS 5 admin dashboard and navigate to Settings > About or Settings > Firmware to view the current firmware version. Alternatively, access the device via SSH and run: cat /etc/version or cat /mnt/boot/version/VERSION 2>/dev/null
    Affected if The firmware version displayed is less than 5.26.300 (for example, 5.26.200, 5.25.x, etc.)
  3. Confirm the CGI component is present
    Verify the device web interface is accessible by navigating to the admin URL (typically http://[device-ip]/admin/ or http://[device-ip]/cgi-bin/). The CGI binary that contains the vulnerability should exist on the device.
    Affected if The device web interface and CGI component are accessible and the firmware version is below 5.26.300
  4. Verify authentication is enabled
    Confirm that user authentication is configured on the device by checking if the login page is active at the admin interface. The vulnerability requires valid credentials to exploit.
    Affected if The device accepts authentication and the firmware version is below 5.26.300

The environment is affected if it is a Western Digital My Cloud OS 5 device running firmware version lower than 5.26.300 with the web interface and CGI component 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
Upgrade available Upgrade to 5.26.300 or later
Fixed in 5.26.300
Interim mitigation

Upgrade Western Digital My Cloud OS 5 devices to firmware version 5.26.300 or later to remediate this vulnerability.

Recommended fix High confidence

5.26.300

  1. Log into the My Cloud OS 5 device administration interface
  2. Navigate to Settings > Firmware or Settings > About to check the current firmware version
  3. If the version is below 5.26.300, download the firmware update from Western Digital's official support website for your specific My Cloud model
  4. Follow the on-screen instructions or refer to the user manual to apply the firmware update, typically found under Settings > Firmware > Update
  5. After the update completes, verify the firmware version shows 5.26.300 or later to confirm the remediation

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

Fix this in My Cloud Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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