CVE-2020-15925
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 at a tpf URI in Loway QueueMetrics before 19.10.21 allows remote authenticated attackers to execute arbitrary SQL commands via the TPF_XPAR1 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 confidenceA SQL injection vulnerability exists in the TPF URI handler of Loway QueueMetrics versions prior to 19.10.21. The vulnerability allows remote authenticated attackers to execute arbitrary SQL commands by injecting malicious payload through the TPF_XPAR1 parameter.
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 installationLocate the QueueMetrics web application installation directory and identify the version file or startup script that contains the version number. Common locations include /opt/queuemetrics or within the application WAR file.Affected if QueueMetrics is installed and the version cannot be determined or is below 19.10.21
-
Check installed version against vulnerability rangeExamine the version number found in the installation. Compare it numerically to 19.10.21. Versions like 19.10.20, 19.08.x, or any version prior to 19.10.21 are affected.Affected if The installed version is any release prior to 19.10.21 (e.g., 19.10.20, 19.10.04, etc.)
-
Verify TPF URI handler is accessibleDetermine if the TPF URI handler endpoint is exposed in the web application. This typically appears as a URL path containing '/tpf/' or similar TPF-related servlets in the QueueMetrics web.xml or application routing configuration.Affected if The TPF handler endpoint is accessible and the application accepts the TPF_XPAR1 parameter without sanitization
-
Review access controls on TPF endpointCheck the authentication configuration for the TPF URI handler. Determine whether unauthenticated or low-privilege users can submit requests to the TPF_XPAR1 parameter.Affected if The TPF handler accepts requests from authenticated users who should not have SQL execution capabilities
You are affected if QueueMetrics is installed with a version number lower than 19.10.21 and the TPF URI handler is accessible to authenticated users.
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 to obtain the patch. Until then, limit access to trusted authenticated users only and implement strict input validation on the TPF_XPAR1 parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15925 — 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-15925 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