# CVE-2025-66289: OrangeHRM is Vulnerable to Persistent Session Access Due to Missing Invalidation After User Disable and Password Change

> Attackers retain access via active sessions after account disablement or password changes, bypassing security controls in OrangeHRM.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 29 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-99qp-xh4q-pr9x

## What is CVE-2025-66289?

CVE-2025-66289 is a high-severity authentication bypass vulnerability in orangehrm, published on 29 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application does not invalidate existing sessions when a user is disabled or when a password change occurs, allowing active session cookies to remain valid indefinitely. As a result, a disabled user, or an attacker using a compromised account, can continue to access protected pages and perform operations as long as a prior session remains active. Because the server performs no session revocation or session-store cleanup during these critical state changes, disabling an account or updating credentials has no effect on already-established sessions. This makes administrative disable actions ineffective and allows unauthorized users to retain full access even after an account is closed or a password is reset, exposing the system to prolonged unauthorized use and significantly increasing the impact of account takeover scenarios. This issue has been patched in version 5.8.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Orangehrm Orangehrm.

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

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

## Is CVE-2025-66289 being exploited?

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

## Other vulnerabilities in orangehrm

- [CVE-2007-1193](https://insights.sbomify.com/CVE-2007-1193/): Other in n/a (critical 9.3)
- [CVE-2025-66224](https://insights.sbomify.com/CVE-2025-66224/): OrangeHRM is Vulnerable to Code Execution Through Arbitrary File Write from Sendmail Parameter Injection (critical 9.0)
- [CVE-2019-12839](https://insights.sbomify.com/CVE-2019-12839/): Command injection in n/a (high 8.8)
- [CVE-2025-66225](https://insights.sbomify.com/CVE-2025-66225/): OrangeHRM is Vulnerable to Account Takeover Through Unvalidated Username in Password Reset Workflow (high 8.7)
- [CVE-2024-36428](https://insights.sbomify.com/CVE-2024-36428/): SQL injection in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66289 is a high-severity authentication bypass vulnerability in orangehrm, published on 29 Nov 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-66289 in the wild and no public exploit code.

Affected product: orangehrm. 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-66289/ (Markdown: https://insights.sbomify.com/CVE-2025-66289/index.md)
```

## Sources

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

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