dbcve.org
Manageengine Ad360Application · Zohocorp

CVE-2023-35785

HIGH · 8.1 CVSS v3.1 Published 2023-08-28
Fix available
A fix is available. Upgrade to 4.1 / 4.3 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Zoho ManageEngine Active Directory 360 versions 4315 and below, ADAudit Plus 7202 and below, ADManager Plus 7200 and below, Asset Explorer 6993 and below and 7xxx 7002 and below, Cloud Security Plus 4161 and below, Data Security Plus 6110 and below, Eventlog Analyzer 12301 and below, Exchange Reporter Plus 5709 and below, Log360 5315 and below, Log360 UEBA 4045 and below, M365 Manager Plus 4529 and below, M365 Security Plus 4529 and below, Recovery Manager Plus 6061 and below, ServiceDesk Plus 14204 and below and 143xx 14302 and below, ServiceDesk Plus MSP 14300 and below, SharePoint Manager Plus 4402 and below, and Support Center Plus 14300 and below are vulnerable to 2FA bypass via a few TOTP authenticators. Note: A valid pair of username and password is required to leverage this vulnerability.

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
How this class of weakness works · CWE-287

The mechanism that verifies who a user is can be side-stepped or fooled, letting an attacker act as someone they're not. Everything built on top of that identity then becomes untrustworthy. Fixing it means hardening the full authentication flow, including edge cases, tokens, and secondary paths.

General guidance for the improper authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 Ad360Application
Affected:< 4.3= 4.3
Manageengine Adaudit PlusApplication
Affected:< 7.2= 7.2
Manageengine Admanager PlusApplication
Affected:< 7.2= 7.2
Manageengine AssetexplorerApplication
Affected:< 6.9= 6.9= 7.0
Manageengine Cloud Security PlusApplication
Affected:< 4.1= 4.1
Manageengine Datasecurity PlusApplication
Affected:< 6.1= 6.1
Manageengine Eventlog AnalyzerApplication
Affected:< 12.3.0= 12.3.0
Manageengine Exchange Reporter PlusApplication
Affected:< 5.7= 5.7

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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
Upgrade available Upgrade to 4.1 / 4.3 / 5.7 or later
Fixed in 4.14.35.7
Vendor patch www.manageengine.com →
Recommended fix Moderate confidence

Refer to vendor advisory for product-specific fixed versions (e.g., AD360 > 4315, ADAudit Plus > 7202, ADManager Plus > 7200)

  1. 1. Review the official vendor security advisory at https://www.manageengine.com/security/advisory/CVE/CVE-2023-35785.html for your specific product
  2. 2. Identify the exact fixed version for your ManageEngine product from the advisory
  3. 3. Download the corresponding patch or upgrade to the fixed version as specified in the advisory
  4. 4. Test the patch/upgrade in a non-production environment before deploying to production
  5. 5. Apply the patch/upgrade to production systems
  6. 6. Verify that 2FA authentication is working correctly after the patch

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35785 — 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-2023-35785 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