dbcve.org
QurouterOperating system · Qnap

CVE-2024-13087

MEDIUM · 6.7 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 an attacker gains local network access who have also gained an administrator account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following version: QuRouter 2.4.6.028 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 · moderate confidence

A command injection vulnerability in QNAP QHora routers (QuRouter) allows an authenticated attacker with local network access and administrator privileges to execute arbitrary system commands on the affected device.

MitigationUpdate QuRouter firmware to version 2.4.6.028 or later. Additionally, enforce strong administrator credentials and limit local network access to trusted devices as defense-in-depth measures.

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= 2.4.5.032= 2.4.6.028

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

CVSS:3.1/AV:L/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. Check QuRouter firmware version via web interface
    Log in to the QuRouter admin panel (typically at http://192.168.100.1 or the router's IP address). Navigate to System Settings or Administration > Firmware Update. Record the current firmware version displayed.
    Affected if The displayed version matches any of the following: 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, 2.4.5.032, or 2.4.6.028
  2. Check QuRouter firmware version via SSH
    Connect to the router via SSH using an administrator account (port 22 or custom port). Run the command 'qurouterctl version' or 'cat /etc/qurooversion' to retrieve the firmware version.
    Affected if The returned version matches any of the affected versions listed above.
  3. Verify device is a QNAP QHora router running QuRouter
    Confirm the device model is a QNAP QHora series router (such as QHora-322, QHora-522, or QHora-321) and that it is running the QuRouter firmware (not QTS or other firmware). Check the web interface header or the label on the device for model information.
    Affected if The device is a QNAP QHora router running QuRouter firmware and the version is in the affected list.
  4. Confirm administrator access is possible
    Verify that you have administrator-level credentials for the QuRouter interface. Try accessing the admin panel or SSH with an account that has full administrative privileges.
    Affected if Administrator credentials are configured and functional on the device, making command injection possible if an attacker gains those credentials.

The device is affected if it is a QNAP QHora router running QuRouter firmware version 2.4.0.190 through 2.4.6.028 inclusive, as versions up to and including 2.4.6.028 contain the command injection vulnerability.

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

Update QuRouter firmware to version 2.4.6.028 or later. Additionally, enforce strong administrator credentials and limit local network access to trusted devices as defense-in-depth measures.

Recommended fix High confidence

QuRouter 2.4.6.028 or later

  1. 1. Identify the current QuRouter version by accessing the QNAP QHora router administration interface
  2. 2. Navigate to the firmware update section within the router settings
  3. 3. Download and install QuRouter version 2.4.6.028 or later from the official QNAP support page
  4. 4. Verify the upgrade was successful by checking the router's firmware version after reboot

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

Fix this in Qurouter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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