# CVE-2026-22800: PILOS affected by a CSRF via GET request allows unintentional termination of all active video conferences

> An authenticated administrator viewing crafted content can unintentionally terminate all active video conferences due to a CSRF vulnerability in an administrative API endpoint.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-r24c-9p4j-rqw9

## What is CVE-2026-22800?

CVE-2026-22800 is a low-severity vulnerability in THM-Health PILOS, published on 12 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

PILOS (Platform for Interactive Live-Online Seminars) is a frontend for BigBlueButton. Prior to 4.10.0, Cross-Site Request Forgery (CSRF) vulnerability exists in an administrative API endpoint responsible for terminating all active video conferences on a single server. The affected endpoint performs a destructive action but is exposed via an HTTP GET request. Although proper authorization checks are enforced and the endpoint cannot be triggered cross-site, the use of GET allows the action to be implicitly invoked through same-site content (e.g. embedded resources rendered within the application). As a result, an authenticated administrator who views crafted content within the application may unknowingly trigger the endpoint, causing all active video conferences on the server to be terminated without explicit intent or confirmation. This vulnerability is fixed in 4.10.0.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-22800?

It affects 1 product.


Products: Thm Pilos.

## How do I fix CVE-2026-22800?

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

## Is CVE-2026-22800 being exploited?

There is no known exploitation of CVE-2026-22800 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-2025-62781](https://insights.sbomify.com/CVE-2025-62781/): PILOS is missing session regeneration after password change (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22800 and fix it if it is affected.

What it is: CVE-2026-22800 is a low-severity vulnerability in THM-Health PILOS, published on 12 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22800 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-2026-22800/ (Markdown: https://insights.sbomify.com/CVE-2026-22800/index.md)
```

## Sources

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

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