dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-8309

HIGH · 8.1 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
There is an improper privilege management vulnerability identified in ManageEngine's Asset Explorer, ServiceDesk Plus, ServiceDesk Plus MSP, and SupportCenter Plus products by Zohocorp. This vulnerability impacts Asset Explorer versions before 7710, ServiceDesk Plus versions before 15110, ServiceDesk Plus MSP versions before 14940, and SupportCenter Plus versions before 14940.

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 confidence

This is an improper privilege management vulnerability in multiple ManageEngine products. The vulnerability allows authenticated users to potentially elevate their privileges or access resources beyond their assigned role permissions, likely due to insufficient enforcement of privilege boundaries in the application's access control mechanisms.

MitigationUpgrade affected products to version 7710 or later for Asset Explorer, 15110 or later for ServiceDesk Plus, and 14940 or later for ServiceDesk Plus MSP and SupportCenter Plus.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify the installed ManageEngine product and version
    Locate the product's About or Version page in the admin console, or check the installation directory for a version file. For ServiceDesk Plus, check <install_dir>/build.number. For Asset Explorer, check <install_dir>/version.txt. For SupportCenter Plus, check <install_dir>/build.txt.
    Affected if The installed version is lower than 7710 for Asset Explorer, lower than 15110 for ServiceDesk Plus, or lower than 14940 for ServiceDesk Plus MSP and SupportCenter Plus.
  2. Confirm the product is accessible over the network
    Verify the web interface is reachable at the configured host and port (default 8080 for ServiceDesk Plus, 8060 for Asset Explorer).
    Affected if The product is deployed and accessible, making the vulnerability potentially exploitable if authentication is enabled.
  3. Verify authentication is enabled
    Check the admin console under Admin > General Settings > Authentication or similar path to confirm user authentication is not disabled.
    Affected if Authentication is enabled, which is required for authenticated users to exploit the privilege escalation flaw.
  4. Review user role assignments
    Navigate to Admin > Users or Admin > Technicians in the web console to list all user accounts and their assigned roles.
    Affected if Multiple users with non-admin roles exist, as these are the accounts that could potentially elevate privileges.

The environment is affected if any ManageEngine product (Asset Explorer, ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus) is running a version lower than the fixed releases (7710, 15110, or 14940 respectively) with authentication enabled and multiple user roles configured.

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 affected products to version 7710 or later for Asset Explorer, 15110 or later for ServiceDesk Plus, and 14940 or later for ServiceDesk Plus MSP and SupportCenter Plus.

Recommended fix High confidence

Asset Explorer 7710 / ServiceDesk Plus 15110 / ServiceDesk Plus MSP 14940 / SupportCenter Plus 14940

  1. Identify which ManageEngine product is in use (Asset Explorer, ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus)
  2. Check the current installed version of the product
  3. Backup all data and configurations before upgrading
  4. Download the appropriate fixed version from ManageEngine's official website or through the product's built-in update mechanism
  5. For Asset Explorer: upgrade to version 7710 or later
  6. For ServiceDesk Plus: upgrade to version 15110 or later
  7. For ServiceDesk Plus MSP: upgrade to version 14940 or later
  8. For SupportCenter Plus: upgrade to version 14940 or later
Caveat Standard upgrade precautions apply - backup data and test in non-production environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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