Vulnerability in Thm (CVE-2025-62781)
Summary
Vulnerability in Thm (CVE-2025-62781). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.8.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-62781 has been found in Thm.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade Thm to 4.8.0 or later.
If unsure, ask your IT team or search "Thm CVE-2025-62781" on the vendor's site.
CVE-2025-62781 (Thm) — CWE-613 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.8.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-613) exists in Thm.
Check the vendor advisory for the affected versions of Thm.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to 4.8.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Thm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Thm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Thmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Thm to 4.8.0ステージング環境で 4.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。