# CVE-2025-8309: User privilege escalation vulnerability

> Attackers can escalate privileges in ManageEngine ITSM and asset management products due to improper privilege management.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-2v7m-x9p5-qp96

## What is CVE-2025-8309?

CVE-2025-8309 is a high-severity vulnerability in ManageEngine Asset Explorer, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-8309?


## How do I fix CVE-2025-8309?

No fix has been published for CVE-2025-8309 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8309 being exploited?

There is no known exploitation of CVE-2025-8309 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8309 and fix it if it is affected.

What it is: CVE-2025-8309 is a high-severity vulnerability in ManageEngine Asset Explorer, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8309 in the wild and no public exploit code.

Affected product: ManageEngine Asset Explorer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8309/ (Markdown: https://insights.sbomify.com/CVE-2025-8309/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8309
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8309
- OSV: https://osv.dev/vulnerability/CVE-2025-8309

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8309/
Summaries are generated and may contain mistakes; the official description above is the record.