CVE-2020-15884
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 TableQuery.php in MunkiReport before 5.6.3 allows attackers to execute arbitrary SQL commands via the order[0][dir] field on POST requests to /datatables/data.
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 MunkiReport's TableQuery.php where the order[0][dir] POST parameter on /datatables/data is not properly sanitized before being used in SQL queries. Attackers can inject arbitrary SQL commands through this parameter, potentially allowing data exfiltration, modification, or database 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< 5.6.3CVSS 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 MunkiReport versionLocate the version file (typically version.php in the root or application/config directory) or access the MunkiReport admin dashboard to view the installed version number.Affected if The installed version is lower than 5.6.3
-
Locate TableQuery.phpFind the TableQuery.php file in the MunkiReport installation directory (commonly in application/libraries or similar path depending on the codebase structure).Affected if The file exists and is present in the installation
-
Inspect the order parameter handlingOpen TableQuery.php and search for code handling the 'order' POST parameter, specifically looking for direct use of $_POST['order'] or similar in SQL query construction without proper sanitization.Affected if The code directly uses the order[0][dir] POST parameter in SQL queries without prepared statements or escaping
-
Verify datatables endpoint accessibilityCheck if the /datatables/data endpoint is accessible by attempting to access it directly via browser or curl, or by reviewing web server configuration and access logs.Affected if The /datatables/data endpoint is reachable and responds to requests
You are affected if MunkiReport version is below 5.6.3 and the vulnerable TableQuery.php file contains unsanitized SQL query construction using the order[0][dir] POST parameter on the accessible /datatbles/data endpoint.
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 data5.6.3
Update MunkiReport to version 5.6.3 or later. As an immediate workaround, restrict access to /datatables/data endpoints and implement web application firewall rules to detect and block SQL injection patterns.
- Consultation4.0 h
- Implementation6.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 $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15884 — 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-15884 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