CVE-2020-15947
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 in the qm_adm/qm_export_stats_run.do endpoint of Loway QueueMetrics before 19.10.21 allows remote authenticated users to execute arbitrary SQL commands via the exportId parameter.
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 · high confidenceSQL injection vulnerability in Loway QueueMetrics allows remote authenticated attackers to execute arbitrary SQL commands through the exportId parameter in the qm_adm/qm_export_stats_run.do endpoint. The lack of proper input sanitization or parameterized queries enables SQL injection attacks. Upgrading to version 19.10.21 or later addresses 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< 19.10.21CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify QueueMetrics installation and versionLocate the QueueMetrics installation directory and check the version file or about page. Common locations include /opt/queuemetrics or the application startup logs.Affected if The installed version is lower than 19.10.21
-
Confirm the qm_adm module is accessibleVerify that the qm_adm/qm_export_stats_run.do endpoint exists and is reachable in the web application. Check web server configuration or application routing.Affected if The qm_adm endpoint is publicly or widely accessible without additional access controls
-
Verify authentication is required for the endpointReview authentication configuration for the qm_adm module. Check if the endpoint is protected by login requirements or if anonymous access is permitted.Affected if The qm_adm endpoint can be accessed without valid authentication or by low-privilege users
-
Check for existing SQL injection protectionInspect any web application firewall (WAF) rules, input filtering, or parameterized query implementations in place for the exportId parameter.Affected if No input validation or SQL injection protection exists for the exportId parameter
A user is affected if they run QueueMetrics version lower than 19.10.21 and have the qm_adm/qm_export_stats_run.do endpoint accessible to authenticated users, since the exportId parameter lacks proper input sanitization.
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.
From vendor data19.10.21
Upgrade to QueueMetrics version 19.10.21 or later. As a temporary mitigation, restrict access to the qm_adm endpoint to only trusted users and implement web application firewall rules to detect and block SQL injection attempts.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15947 — 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-2020-15947 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