CVE-2025-1724
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 · uneditedZohocorp's ManageEngine Analytics Plus and Zoho Analytics on-premise versions older than 6130 are vulnerable to an AD only account takeover because of a hardcoded sensitive token.
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 confidenceManageEngine Analytics Plus and Zoho Analytics on-premise versions before 6130 contain a hardcoded sensitive token that allows attackers to perform Active Directory account takeover. The vulnerability stems from a default credentials-like token embedded in the software that can be exploited to hijack AD-authenticated user accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 the installed versionLocate the version number in the product's About or System Information page, or check the installation directory for a version file. Common paths include the product's admin console or configuration files in the installation folder.Affected if The installed version is ManageEngine Analytics Plus or Zoho Analytics on-premise and is lower than 6130.
-
Confirm the exact build or patch versionAccess the product's administrator interface and navigate to the Support or About section to retrieve the full version string including build number.Affected if The version/build number is below 6130 (for example, 6120, 6100, or any version preceding 6130).
-
Verify Active Directory integration statusCheck the product's authentication settings or AD integration configuration panel to determine whether Active Directory or LDAP authentication is enabled.Affected if Active Directory integration is enabled and the product version is below 6130, making the hardcoded token applicable to hijack AD-authenticated accounts.
-
Review recent AD authentication eventsExamine authentication and audit logs within the product for unexpected account activity, particularly successful logins using accounts or methods that were not explicitly configured.Affected if Unusual AD account activity is found in logs and the product version is below 6130.
You are affected if ManageEngine Analytics Plus or Zoho Analytics on-premise is installed with a version lower than 6130 and Active Directory integration is enabled.
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 · scopedUpgrade to version 6130 or later and rotate any credentials or tokens that may have been exposed. Verify AD integration is functioning correctly post-upgrade and review audit logs for signs of exploitation.
Version 6130 or later of ManageEngine Analytics Plus / Zoho Analytics on-premise
- Upgrade ManageEngine Analytics Plus (Zoho Analytics on-premise) to version 6130 or later to resolve the hardcoded sensitive token vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1724 — 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-2025-1724 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