CVE-2020-15394
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 · uneditedThe REST API in Zoho ManageEngine Applications Manager before build 14740 allows an unauthenticated SQL Injection via a crafted request, leading to Remote Code Execution.
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 confidenceAn unauthenticated SQL injection vulnerability exists in the REST API of Zoho ManageEngine Applications Manager builds prior to 14740. Attackers can craft malicious SQL queries through the API endpoint to inject arbitrary SQL commands, which can be leveraged to achieve remote code execution on the underlying system.
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< 14.0= 14.0CVSS 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 Applications Manager installationLocate Zoho ManageEngine Applications Manager in your environment - check installed software listings, service status, or running processes on servers where it may be deployed.Affected if The software is present and running.
-
Identify the build versionAccess the Applications Manager admin console or check the product's About/Version section to retrieve the exact build number.Affected if The build number is below 14740, or the version is listed as 14.0 or earlier.
-
Verify REST API exposureCheck the Applications Manager configuration to determine if the REST API interface is enabled and accessible.Affected if The REST API is enabled and exposed to network traffic.
-
Assess network accessibilityDetermine if the REST API endpoint is reachable from untrusted networks or external IP ranges.Affected if The API is accessible without authentication or from less-trusted network segments.
Your environment is affected if Zoho ManageEngine Applications Manager is running with a build version below 14740 (or version 14.0) and the REST API is accessible to potential attackers.
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 · scoped14.0
Upgrade Zoho ManageEngine Applications Manager to build 14740 or later. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access to the application's REST API interface.
Build 14740 (or later)
- Download ManageEngine Applications Manager build 14740 or later from the official ManageEngine website
- Ensure you have a backup of the current installation and database before upgrading
- Stop the Applications Manager service before upgrading
- Install the updated build following standard ManageEngine upgrade procedures
- After installation, start the Applications Manager service
- Verify the REST API functionality is working correctly after the upgrade
- Confirm the build number reflects the fix (build 14740 or higher)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15394 — 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-15394 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