CVE-2024-50389
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 · uneditedA SQL injection vulnerability has been reported to affect QuRouter. If exploited, the vulnerability could allow remote attackers to inject malicious code. 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 · moderate confidenceA SQL injection vulnerability in QuRouter allows remote attackers to inject malicious code through unsanitized user input that gets incorporated into database queries. With a CVSS score of 9.8, this critical flaw enables attackers to potentially execute arbitrary commands on the underlying database, leading to data exfiltration or complete system compromise.
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.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.106CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed firmware versionLog into the QuRouter admin interface (typically via http://router-ip or https://router-ip) and navigate to System Settings > Firmware Update or System Status to view the current firmware version. Alternatively, access the router via CLI if available and run 'version' or 'show firmware' command.Affected if The displayed firmware version matches any of these exact versions: 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
-
Verify web management interface is exposedAttempt to access the QuRouter login page from a browser using the router's IP address (commonly http://192.168.1.1 or the IP assigned to the router). Confirm the page loads and displays the QuRouter login form.Affected if The web administrative interface is reachable from the network (especially from untrusted networks such as the internet)
-
Check for unauthorized access indicatorsReview router logs for suspicious SQL-like patterns in HTTP requests. Look for unusual characters like single quotes ('), UNION SELECT, OR 1=1, or other SQL syntax in request parameters. Access logs via System Settings > System Log or similar.Affected if Log entries contain SQL injection patterns or unexpected database error messages, indicating possible exploitation attempts
You are affected if your QuRouter firmware version exactly 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 AND the web interface is accessible from a network where attackers could send HTTP requests.
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 immediately to QuRouter version 2.4.5.032 or later to remediate the vulnerability. If upgrading is not immediately feasible, restrict network access to the administrative interface and monitor for suspicious database query patterns.
QuRouter 2.4.5.032 or later
- Identify the current QuRouter firmware version through the device management interface
- If the installed version is 2.4.0.190, 2.4.1.172, 2.4.1.634, or 2.4.2.317, download and install QuRouter version 2.4.5.032 or later from the official QNAP website
- Verify the upgrade was successful by checking the firmware version in the QuRouter management console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50389 — 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-2024-50389 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