CVE-2020-15533
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 · uneditedIn Zoho ManageEngine Application Manager 14.7 Build 14730 (before 14684, and between 14689 and 14750), the AlarmEscalation module is vulnerable to unauthenticated SQL Injection attack.
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 confidenceUnauthenticated SQL Injection vulnerability in the AlarmEscalation module of Zoho ManageEngine Application Manager allows remote attackers to inject malicious SQL queries via unsanitized input, potentially leading to complete database compromise, data exfiltration, or remote code execution.
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.6= 14.6= 14.7CVSS 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.
-
Identify installed Application Manager versionAccess the product's About or Version information page, typically found in the admin console under Help > About, or check the build number displayed on the login pageAffected if The version is 14.6, 14.7, or any version earlier than 14.6 (e.g., 14.5, 14.0, etc.)
-
Compare version against affected build rangeLocate the build number in the version details; the vulnerable builds include version 14.6 and 14.7, with fixes starting at build 14684 (excluding the sub-range 14689-14750 which also contains fixes)Affected if The build number is 14684 or lower, or falls within 14689-14750, indicating an unpatched vulnerable version
-
Verify AlarmEscalation module accessibilityConfirm whether the AlarmEscalation functionality is accessible within the application; this module is typically available through the admin or operations interfaceAffected if The AlarmEscalation module is present and accessible (the vulnerability exists in this module regardless of whether it is actively used)
-
Assess network exposure of the application interfaceDetermine if the Application Manager web console is exposed to untrusted networks or the internet by checking firewall rules, NAT configurations, or reverse proxy settingsAffected if The application is reachable from untrusted network segments or the internet, allowing unauthenticated attackers to reach the vulnerable endpoint
The environment is affected if the installed version is 14.6 or 14.7 (or any version below 14.6) and the web interface is network-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.
From vendor data14.6
Apply vendor patch to upgrade to build 14684 or later (excluding the vulnerable range 14689-14750), or upgrade to the latest stable release. If immediate patching is not possible, restrict network access to the Application Manager interface.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15533 — 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-15533 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