dbcve.org
QurouterOperating system · Qnap

CVE-2024-50390

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-07
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
A command injection vulnerability has been reported to affect QHora. If exploited, the vulnerability could allow remote attackers to execute arbitrary commands. We have already fixed the vulnerability in the following version: QuRouter 2.4.5.032 and later

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

A command injection vulnerability in QNAP's QuRouter firmware (affecting QHora Wi-Fi 6 routers) allows remote attackers to execute arbitrary operating system commands through unsanitized input. This is a pre-authentication critical vulnerability with CVSS 9.8, indicating ease of exploitation and severe impact on confidentiality, integrity, and availability.

MitigationApply QuRouter firmware version 2.4.5.032 or later to remediate the command injection vulnerability. Organizations should prioritize patching given the critical severity and remote attack vector.

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
QurouterOperating system
Affected:= 2.4.0.190= 2.4.1.172= 2.4.1.634= 2.4.2.317= 2.4.2.538= 2.4.3.103= 2.4.4.106

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check QuRouter firmware version via web admin interface
    Log into the QuRouter admin panel (typically http://192.168.100.1 or http://qurouter.local). Navigate to System Settings > System > Firmware Version. Record the displayed version number.
    Affected if The displayed firmware version matches any of these: 2.4.0.190, 2.4.1.172, 2.4.1.634, 2.4.2.317, 2.4.2.538, 2.4.3.103, or 2.4.4.106
  2. Check firmware version via command line interface
    Access the router CLI via SSH or telnet if enabled. Run the command 'qurouterctl version' or 'cat /proc/version' to retrieve the firmware build. Record the version string.
    Affected if The version output matches any of the affected versions listed above.
  3. Verify QuRouter HTTP service is accessible
    From an external network perspective, confirm the QuRouter web interface is reachable by attempting an HTTP request to the router's WAN IP address on ports 80 or 443.
    Affected if The QuRouter admin interface is exposed to the WAN/internet and the firmware version is one of the affected versions listed.
  4. Check for fixed firmware version
    If firmware version can be retrieved, compare it to the fixed version 2.4.5.032 or later.
    Affected if The installed firmware version is below 2.4.5.032, placing it in the affected version range.

The device is affected if the QuRouter firmware version running on the QHora Wi-Fi 6 router matches any of the seven specific vulnerable versions (2.4.0.190 through 2.4.4.106) or is any version earlier than the patched release 2.4.5.032.

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

Apply QuRouter firmware version 2.4.5.032 or later to remediate the command injection vulnerability. Organizations should prioritize patching given the critical severity and remote attack vector.

Recommended fix High confidence

QuRouter 2.4.5.032 or later

  1. Log in to the QuRouter administrative web interface
  2. Navigate to the Firmware Update or System Settings section
  3. Download the QuRouter firmware version 2.4.5.032 or later from the official QNAP website
  4. Upload and install the firmware file through the web interface
  5. Wait for the router to reboot and apply the update
  6. Verify that the router is running version 2.4.5.032 or later by checking the firmware version in the admin interface
Caveat Review QNAP release notes for QuRouter 2.4.5.032 to check for any configuration or feature changes before upgrading

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

Fix this in Qurouter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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