CVE-2021-46166
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 · uneditedZoho ManageEngine Desktop Central before 10.0.662 allows authenticated users to obtain sensitive information from the database by visiting the Reports page.
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 · moderate confidenceZoho ManageEngine Desktop Central before version 10.0.662 contains an information disclosure vulnerability in the Reports functionality. Authenticated users with standard privileges can exploit the Reports page to query and retrieve sensitive data directly from the underlying database, including potentially confidential system or user information.
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< 10.0.662CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 ManageEngine Desktop Central versionAccess the Desktop Central admin console and navigate to the About or System Settings page to view the build version. Alternatively, check the installation directory for a version file or access the help > about section in the client.Affected if The installed version number is lower than 10.0.662 (for example, 10.0.661, 10.0.650, etc.)
-
Confirm Reports module is accessibleLog into the Desktop Central web interface and verify the Reports functionality is available in the navigation menu. Check if the Reports module is enabled in the admin settings.Affected if The Reports module is present and accessible to standard user accounts
-
Verify user account privilegesAccess the admin console User/Account Management section and review the list of users and their assigned roles. Identify accounts with standard or basic user privileges (not administrator).Affected if There exist user accounts with standard (non-admin) privileges who have access to the Reports functionality
-
Test Reports functionality for direct database query capabilityAs a standard user, navigate to the Reports section and examine whether arbitrary SQL-like queries or direct database field selections can be made without proper sanitization or restriction.Affected if Standard users can construct custom reports that query underlying database tables directly
Your environment is affected if ManageEngine Desktop Central is installed at a version lower than 10.0.662 and standard user accounts have access to the Reports module, allowing them to query underlying database content.
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 · scoped10.0.662
Apply the vendor patch by upgrading ManageEngine Desktop Central to version 10.0.662 or later. Review user access controls and audit existing accounts for unauthorized data access following the upgrade.
10.0.662
- Check current ManageEngine Desktop Central version by navigating to the Admin or About page in the application
- Review the official ManageEngine release notes and upgrade documentation at www.manageengine.com for detailed upgrade procedures
- Ensure you have a complete backup of the database and configuration files before upgrading
- Download Desktop Central version 10.0.662 or later from the official ManageEngine portal
- Execute the upgrade following the vendor's documented upgrade path, which may include stopping services, running the installer, and validating the upgrade
- After upgrade, verify the Reports page functionality and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46166 — 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-2021-46166 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