CVE-2025-62846
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 · uneditedAn SQL injection vulnerability has been reported to affect QHora. If a local attacker gains an administrator account, they can then exploit the vulnerability to execute unauthorized code or commands. 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 confidenceSQL injection vulnerability in QHora devices allows a local attacker with administrator credentials to execute unauthorized code or commands through malicious SQL queries.
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= 2.6.0.239= 2.6.0.688= 2.6.1.028CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is QHora or QurouterLog into the device admin interface or check the device label/marketing materials to verify the exact model name is QHora or QurouterAffected if Device is not a QHora or Qurouter model - this vulnerability does not apply
-
Identify installed firmware versionAccess the device admin panel, typically under System > Firmware or Settings > About, to view the current firmware version numberAffected if Firmware version cannot be determined or accessed
-
Compare firmware version to affected releasesCompare your installed firmware version against these exact versions: 2.6.0.239, 2.6.0.688, 2.6.1.028 - note that matching any one of these specific versions means you are affectedAffected if Installed version exactly matches 2.6.0.239 OR 2.6.0.688 OR 2.6.1.028
-
Verify administrator credentials existCheck if there are administrator user accounts configured on the device - the vulnerability requires valid administrator credentials to exploit the SQL injectionAffected if No administrator accounts are configured or credentials are unknown
You are affected only if your device is a QHora or Qurouter running exactly firmware version 2.6.0.239, 2.6.0.688, or 2.6.1.028 and you have administrator credentials configured.
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 · scopedUpgrade QuRouter firmware to version 2.6.2.007 or later. Enforce strong administrator passwords and restrict local access to prevent credential compromise.
QuRouter 2.6.2.007 or later
- Log in to the QNAP QHora router web administration interface
- Navigate to the firmware update or system settings section
- Check the current QuRouter firmware version (verify it is 2.6.0.239, 2.6.0.688, or 2.6.1.028)
- Download and install QuRouter version 2.6.2.007 or later from the QNAP download center
- After the upgrade completes, verify the new firmware version is 2.6.2.007 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62846 — 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-2025-62846 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