CVE-2020-15882
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 CSRF issue in manager/delete_machine/{id} in MunkiReport before 5.6.3 allows attackers to delete arbitrary machines from the MunkiReport database.
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 confidenceThis is a CSRF (Cross-Site Request Forgery) vulnerability in MunkiReport's manager/delete_machine/{id} endpoint. The application fails to validate anti-CSRF tokens on the machine deletion function, allowing authenticated users to be tricked into unknowingly deleting arbitrary machines from the database via malicious requests from other sites.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 installed MunkiReport versionLocate the version file or check the version reported in the MunkiReport web interface (typically in the footer or in admin/settings). Alternatively, check for a version.php or similar file in the application root directory.Affected if The installed version is lower than 5.6.3
-
Examine the delete_machine controller codeLocate the manager/delete_machine endpoint in the MunkiReport codebase (usually in app/controllers/Manager.php or similar). Inspect the delete_machine function to see if it performs anti-CSRF token validation before processing the deletion request.Affected if The delete_machine function lacks any call to verify a CSRF token or does not validate the CSRF token on POST requests
-
Check the application's CSRF protection configurationReview the application configuration files (such as config.php, app.php, or the framework's CSRF middleware) to confirm whether global CSRF token validation is enabled and enforced for POST requests.Affected if CSRF protection is disabled in the configuration or the delete_machine endpoint is excluded from CSRF validation rules
-
Verify token presence in deletion request flowIf the application uses a CSRF token framework, trace how the machine deletion form or API call handles the token - check whether the view template for machine deletion includes a valid CSRF token field and whether the backend validates it.Affected if The machine deletion form or API does not require or validate an anti-CSRF token
A user is affected if their MunkiReport installation is version 5.6.2 or lower AND the manager/delete_machine/{id} endpoint does not validate anti-CSRF tokens on POST 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.
From vendor data5.6.3
Upgrade MunkiReport to version 5.6.3 or later which includes CSRF token validation. Alternatively, implement anti-CSRF tokens on the delete_machine endpoint and validate them on every POST request.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15882 — 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-15882 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