{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-62524 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62524 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-62524 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-62524 in the wild and no public exploit code.\n\nAffected product: THM-Health PILOS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62524/ (Markdown: https://insights.sbomify.com/CVE-2025-62524/index.md)","id":"CVE-2025-62524","markdown":"https://insights.sbomify.com/CVE-2025-62524/index.md","name":"CVE-2025-62524","record":{"aliases":["GHSA-q93h-5j6h-j22x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PILOS frontend","requires_auth":"none","summary":"Attackers can fingerprint the server by exposing the PHP version via headers and footer, facilitating targeted exploit attempts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pilos","vendor":"thm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"PILOS Exposes PHP version","id":"CVE-2025-62524","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"OpenWrt vulnerable to local privilage escalation","id":"CVE-2025-62525"},"packages":[],"prev":{"headline":"PILOS Misconfigured the Access-Control-Allow-Origin Header","id":"CVE-2025-62523"},"products":["PILOS"],"published":"2025-10-27","related":[{"cvss_score":8.8,"headline":"PILOS account takeover through password reset poisoning","id":"CVE-2023-47107","kev_date_added":null,"published":"2023-11-08"},{"cvss_score":6.3,"headline":"PILOS Misconfigured the Access-Control-Allow-Origin Header","id":"CVE-2025-62523","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":5,"headline":"PILOS is missing session regeneration after password change","id":"CVE-2025-62781","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":2.4,"headline":"PILOS affected by a CSRF via GET request allows unintentional termination of all active video conferences","id":"CVE-2026-22800","kev_date_added":null,"published":"2026-01-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-27","vendors":["THM-Health"]},"summary":"Attackers can fingerprint the server by exposing the PHP version via headers and footer, facilitating targeted exploit attempts.","url":"https://insights.sbomify.com/CVE-2025-62524/"}