dbcve.org
QurouterOperating system · Qnap

CVE-2025-62844

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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 weak authentication vulnerability has been reported to affect QHora. If an attacker gains local network access, they can then exploit the vulnerability to gain sensitive information. We have already fixed the vulnerability in the following version: QuRouter 2.6.2.007 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

This is a weak authentication vulnerability in QNAP QHora routers. An attacker with local network access can exploit weak authentication mechanisms to gain sensitive information. The vulnerability is fixed in QuRouter version 2.6.2.007 and later.

MitigationUpgrade QHora routers to QuRouter 2.6.2.007 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
QurouterOperating system
Affected:= 2.6.0.239= 2.6.0.688= 2.6.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 QHora router admin panel (typically at http://192.168.1.1 or http://192.168.100.1), navigate to System Settings > Firmware Update or System Status, and record the displayed QuRouter version number.
    Affected if The installed version matches exactly 2.6.0.239, 2.6.0.688, or 2.6.1.028
  2. Check QuRouter firmware version via CLI
    Connect to the QHora router via SSH or telnet (if enabled), log in with admin credentials, and run the command 'cat /proc/version' or 'fw_printenv' to retrieve the firmware version.
    Affected if The installed version matches exactly 2.6.0.239, 2.6.0.688, or 2.6.1.028
  3. Verify remote administration is accessible
    From a computer on the local network, confirm the router admin interface is accessible via HTTP/HTTPS. This vulnerability requires local network access to exploit, so verify the admin portal is reachable.
    Affected if The admin interface is accessible from the local network on versions 2.6.0.239, 2.6.0.688, or 2.6.1.028
  4. Check for default or weak admin credentials
    Attempt to log into the router admin interface with default credentials (admin/admin, admin/qnap, etc.) or verify if weak authentication methods are in use. The vulnerability relates to weak authentication mechanisms.
    Affected if Default credentials work or weak authentication is enabled on versions 2.6.0.239, 2.6.0.688, or 2.6.1.028

You are affected if your QHora router runs QuRouter version 2.6.0.239, 2.6.0.688, or 2.6.1.028 and the admin interface is accessible from your local network.

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 QHora routers to QuRouter 2.6.2.007 or later to remediate this vulnerability.

Recommended fix High confidence

QuRouter 2.6.2.007 or later

  1. 1. Log in to the QNAP QuRouter admin interface
  2. 2. Navigate to the Firmware Update or System Settings section
  3. 3. Check the current firmware version to confirm it is one of the affected versions (2.6.0.239, 2.6.0.688, or 2.6.1.028)
  4. 4. Initiate a firmware update to check for the latest available version
  5. 5. Download and install QuRouter version 2.6.2.007 or later
  6. 6. After the update completes, verify the firmware version has been successfully updated
  7. 7. Restart the device if prompted to ensure all changes take effect

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

Fix this in Qurouter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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