dbcve.org
QurouterOperating system · Qnap

CVE-2025-62845

MEDIUM · 6.7 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 →
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
An improper neutralization of escape, meta, or control sequences vulnerability has been reported to affect QHora. If a local attacker gains an administrator account, they can then exploit the vulnerability to cause unexpected behavior. We have already fixed the vulnerability in the following version: QuRouter 2.6.3.009 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

Improper neutralization of escape, meta, or control sequences in QNAP QHora routers allows a local attacker with administrator privileges to inject or interpret special character sequences, causing unexpected behavior. This is a classic input validation/sanitization failure affecting the router's administrative interface.

MitigationUpgrade QuRouter to version 2.6.3.009 or later. Restrict administrator account access, monitor for unauthorized admin creation, and enforce strong password policies to limit the attack surface.

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= 2.6.2.007

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 router firmware version via web interface
    Log into the QNAP QHora administrative web interface (typically at https://<router-ip>), navigate to System Settings or System > Firmware Update, and locate the current firmware version displayed.
    Affected if The displayed firmware version matches 2.6.0.239, 2.6.0.688, 2.6.1.028, or 2.6.2.007 exactly.
  2. Check router firmware version via CLI
    Access the router via SSH (default port 22) using administrator credentials and run the command to display system version information, such as 'version' or 'show version' or 'get system info'.
    Affected if The CLI output shows firmware version 2.6.0.239, 2.6.0.688, 2.6.1.028, or 2.6.2.007.
  3. Verify administrator account access exists
    From the web interface, navigate to Administration > Admin Users or Account Settings and confirm whether administrator-level accounts are configured or accessible.
    Affected if Any administrator-level account exists on the router, as the vulnerability requires local attacker with administrator privileges to exploit.
  4. Check for unauthorized admin accounts
    Review the list of all user accounts in the administrative interface and verify that all accounts with administrator privileges are expected and were created by authorized personnel.
    Affected if Unexpected or unauthorized administrator accounts are present, indicating potential exploitation or attempt to leverage this vulnerability.

The environment is affected if the QNAP QHora router runs firmware version 2.6.0.239, 2.6.0.688, 2.6.1.028, or 2.6.2.007 and has any administrator account configured.

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 QuRouter to version 2.6.3.009 or later. Restrict administrator account access, monitor for unauthorized admin creation, and enforce strong password policies to limit the attack surface.

Recommended fix High confidence

QuRouter 2.6.3.009 or later

  1. 1. Back up current router configuration
  2. 2. Download QuRouter firmware version 2.6.3.009 or later from the official QNAP website
  3. 3. Access the QHora router admin interface
  4. 4. Navigate to the firmware update section
  5. 5. Upload and install the new firmware version
  6. 6. After reboot, verify the firmware version in the admin interface
Caveat Router firmware upgrades may temporarily interrupt network connectivity; ensure you have a recovery plan

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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