# CVE-2025-62524: PILOS Exposes PHP version

> Attackers can fingerprint the server by exposing the PHP version via headers and footer, facilitating targeted exploit attempts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-q93h-5j6h-j22x

## What is CVE-2025-62524?

CVE-2025-62524 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, with no action from the victim.

### Official description

PILOS (Platform for Interactive Live-Online Seminars) is a frontend for BigBlueButton. PILOS before 4.8.0 exposes the PHP version via the X-Powered-By header, enabling attackers to fingerprint the server and assess potential exploits. This information disclosure vulnerability originates from PHP’s base image. Additionally, the PHP version can also be inferred through the PILOS version displayed in the footer and by examining the source code available on GitHub. This information disclosure vulnerability has been patched in PILOS in v4.8.0.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Thm Pilos.

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

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

## Is CVE-2025-62524 being exploited?

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

What it is: CVE-2025-62524 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, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62524 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-62524/ (Markdown: https://insights.sbomify.com/CVE-2025-62524/index.md)
```

## Sources

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

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