CVE-2026-9773
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 · uneditedUnraid Web Server ToggleState Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Unraid. Authentication is required to exploit this vulnerability. The specific flaw exists within ToggleState.php. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the www-data user. Was ZDI-CAN-30134.
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 confidenceCommand injection vulnerability in Unraid's ToggleState.php allows authenticated remote attackers to execute arbitrary code by injecting shell commands through unsanitized user input that gets passed to a system call.
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< 7.3.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Unraid versionCheck the Unraid web UI (top-right corner shows version) or run 'ls -la /etc/unraid-version' or 'cat /etc/unraid-version'Affected if Version is below 7.3.0 (e.g., 7.2.x, 7.1.x, 7.0.x, 6.x series)
-
Locate ToggleState.phpFind ToggleState.php in the web root - typically in /usr/local/emhttp/plugins/ or under the web interface directory structureAffected if File exists on the system (indicating the vulnerable component is present)
-
Check authentication configurationReview user access controls - look at /etc/lighttpd/lighttpd.conf or the users settings file to see if remote API access is enabledAffected if Remote authentication/API access is enabled for users (especially non-admin accounts)
-
Inspect ToggleState.php for vulnerable patternsExamine the ToggleState.php file contents for unsanitized user input passed to exec(), shell_exec(), system(), or passthru() callsAffected if Code passes $_POST, $_GET, or similar user-supplied input directly to shell execution functions without sanitization
The environment is affected if running Unraid version below 7.3.0 with ToggleState.php present and remote authentication enabled.
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.
dbcve · scoped7.3.0
Apply vendor patch when available; implement strict input validation and use parameterized APIs instead of shell commands in ToggleState.php.
Unraid OS version 7.3.0 or later
- Log in to the Unraid web interface as an administrator
- Navigate to the 'Tools' or 'System' section
- Look for a system update or OS update option
- Check for and apply any available updates to reach version 7.3.0 or later
- After updating, verify the system is functioning correctly
- Confirm that ToggleState.php has been updated as part of the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9773 — 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-2026-9773 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