# CVE-2025-62781: PILOS is missing session regeneration after password change

> Attackers with stolen session tokens retain access after password changes because the current session token is not regenerated, allowing continued unauthorized access.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 27 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-m8w5-8w3h-72wm

## What is CVE-2025-62781?

CVE-2025-62781 is a medium-severity vulnerability in THM-Health PILOS, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PILOS (Platform for Interactive Live-Online Seminars) is a frontend for BigBlueButton. Prior to 4.8.0, users with a local account can change their password while logged in. When doing so, all other active sessions are terminated, except for the currently active one. However, the current session’s token remains valid and is not refreshed. If an attacker has previously obtained this session token through another vulnerability, changing the password will not invalidate their access. As a result, the attacker can continue to act as the user even after the password has been changed. This vulnerability is fixed in 4.8.0.

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

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

It affects 1 product.


Products: Thm Pilos.

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

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

## Is CVE-2025-62781 being exploited?

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

## Other vulnerabilities in THM-Health PILOS

- [CVE-2023-47107](https://insights.sbomify.com/CVE-2023-47107/): PILOS account takeover through password reset poisoning (high 8.8)
- [CVE-2025-62523](https://insights.sbomify.com/CVE-2025-62523/): PILOS Misconfigured the Access-Control-Allow-Origin Header (medium 6.3)
- [CVE-2025-62524](https://insights.sbomify.com/CVE-2025-62524/): PILOS Exposes PHP version (medium 5.3)
- [CVE-2026-22800](https://insights.sbomify.com/CVE-2026-22800/): PILOS affected by a CSRF via GET request allows unintentional termination of all active video conferences (low 2.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62781 is a medium-severity vulnerability in THM-Health PILOS, published on 27 Oct 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-62781 in the wild and no public exploit code.

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

## Sources

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

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