dbcve.org
Manageengine Applications ManagerApplication · Zohocorp

CVE-2020-27995

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SQL Injection in Zoho ManageEngine Applications Manager 14 before 14560 allows an attacker to execute commands on the server via the MyPage.do template_resid parameter.

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 confidence

A SQL injection vulnerability exists in Zoho ManageEngine Applications Manager versions before 14 build 14560. The flaw is in the MyPage.do endpoint through the template_resid parameter, allowing unauthenticated attackers to inject malicious SQL queries. Successful exploitation can lead to complete database compromise and remote code execution on the underlying server.

MitigationUpgrade Zoho ManageEngine Applications Manager to version 14 build 14560 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the affected endpoint and implement WAF rules to detect SQL injection attempts.

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
Manageengine Applications ManagerApplication
Affected:= 14.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Zoho ManageEngine Applications Manager is installed
    Look for Applications Manager running on the server or check for its installation directory. Common default paths may include C:\ManageEngine\ApplicationsManager or /opt/ManageEngine/ApplicationsManager on Linux. Verify the service is running.
    Affected if Applications Manager is installed and running on the system
  2. Identify the installed version and build number
    Access the Applications Manager web interface and navigate to the About or Settings page to view the version information. Alternatively, check the build.info or version file in the installation directory if accessible.
    Affected if The version is 14.0 but the build number is below 14560, or the version cannot be determined but is reported as 14.0
  3. Verify the MyPage.do endpoint is accessible
    Attempt to access the MyPage.do endpoint on the server. Send a request to http(s)://<server>:<port>/MyPage.do or check if the endpoint responds without authentication.
    Affected if The MyPage.do endpoint responds to requests, indicating it is exposed and potentially reachable
  4. Check if the template_resid parameter is accepted
    Send a test request to the MyPage.do endpoint including the template_resid parameter, such as: GET /MyPage.do?template_resid=1. Observe if the parameter is processed and reflected in the response.
    Affected if The template_resid parameter is accepted and processed by the endpoint without requiring authentication

If Applications Manager version 14.0 with build below 14560 is installed AND the MyPage.do endpoint with the template_resid parameter is accessible, the environment is vulnerable to CVE-2020-27995.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zoho ManageEngine Applications Manager to version 14 build 14560 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the affected endpoint and implement WAF rules to detect SQL injection attempts.

Recommended fix High confidence

ManageEngine Applications Manager build 14560 or later (within version 14.x)

  1. 1. Back up the current Applications Manager installation and database
  2. 2. Download Applications Manager version 14560 or later from the official ManageEngine download center (www.manageengine.com)
  3. 3. Stop the Applications Manager service
  4. 4. Upgrade to the downloaded fixed version following ManageEngine's standard upgrade procedure
  5. 5. Start the Applications Manager service
  6. 6. Verify the upgrade was successful by accessing the admin console and confirming normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Applications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27995 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-27995 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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