CVE-2020-8540
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 · uneditedAn XML external entity (XXE) vulnerability in Zoho ManageEngine Desktop Central before the 07-Mar-2020 update allows remote unauthenticated users to read arbitrary files or conduct server-side request forgery (SSRF) attacks via a crafted DTD in an XML request.
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 confidenceXXE vulnerability in Zoho ManageEngine Desktop Central allows remote unauthenticated attackers to embed malicious DTD content in XML requests, enabling file system access to read arbitrary files on the server or conduct SSRF attacks by forcing the server to make requests to attacker-controlled or internal infrastructure endpoints.
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< 2020-03-07CVSS 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.
-
Confirm Zoho ManageEngine Desktop Central is installedLook for the product in installed programs (Windows) or check for /opt/DesktopCentral or similar installation directories (Linux). The product is typically accessed via a web browser on ports 8020, 8383, or 8443.Affected if The product is present on the system
-
Identify the installed versionCheck the product's web interface for version information, typically found in the Help > About page, or examine configuration files in the installation directory for a version.txt or build number file.Affected if The version or build date is before March 7, 2020
-
Locate XML-handling endpointsReview the product's API documentation or web logs for endpoints accepting XML input, commonly found in integration features like LDAP, REST API, or import functions.Affected if The product exposes XML-processing endpoints accessible over the network without authentication
If Zoho ManageEngine Desktop Central is installed and the version predates the March 2020 update, the environment is vulnerable to XXE attacks via unauthenticated XML 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 · scoped2020-03-07
Apply the March 2020 vendor security update from Zoho. If immediate patching is not feasible, consider restricting or disabling XML processing in affected components while ensuring core functionality remains operational.
Any version released on or after March 7, 2020 (the 07-Mar-2020 update or later)
- 1. Identify the current installed version of ManageEngine Desktop Central
- 2. If the installed version predates the 07-Mar-2020 update, plan for an upgrade
- 3. Obtain the latest ManageEngine Desktop Central update from the official vendor (ManageEngine)
- 4. Review the vendor's upgrade instructions and release notes for the post-March-2020 version
- 5. Back up the current installation and database before proceeding
- 6. Apply the upgrade to a version released on or after March 7, 2020
- 7. Verify the upgrade was successful and the XML parsing is now secure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8540 — 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-8540 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