# CVE-2025-62523: PILOS Misconfigured the Access-Control-Allow-Origin Header

> PILOS frontend had a CORS misconfiguration allowing cross-origin requests with credentials, potentially enabling data exfiltration or modification, though mitigated by Laravel session checks.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-pgfw-f4mp-5445

## What is CVE-2025-62523?

CVE-2025-62523 is a medium-severity vulnerability in THM-Health PILOS, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, 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. PILOS before 4.8.0 includes a Cross-Origin Resource Sharing (CORS) misconfiguration in its middleware: it reflects the Origin request header back in the Access-Control-Allow-Origin response header without proper validation or a whitelist, while Access-Control-Allow-Credentials is set to true. This behavior could allow a malicious website on a different origin to send requests (including credentials) to the PILOS API. This may enable exfiltration or actions using the victim’s credentials if the server accepts those cross-origin requests as authenticated. Laravel’s session handling applies additional origin checks such that cross-origin requests are not authenticated by default. Because of these session-origin protections, and in the absence of any other unknown vulnerabilities that would bypass Laravel’s origin/session checks, this reflected-Origin CORS misconfiguration is not believed to be exploitable in typical PILOS deployments. This vulnerability has been patched in PILOS in v4.8.0

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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

It affects 1 product.


Products: Thm Pilos.

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

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

## Is CVE-2025-62523 being exploited?

There is no known exploitation of CVE-2025-62523 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-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)
- [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-62523 and fix it if it is affected.

What it is: CVE-2025-62523 is a medium-severity vulnerability in THM-Health PILOS, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62523 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-62523/ (Markdown: https://insights.sbomify.com/CVE-2025-62523/index.md)
```

## Sources

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

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