SQL Injection in Admin Area's “/admin_area/login_as_user.php” file (CVE-2025-62423)
Summary
SQL injection in Admin Area's “/admin_area/login_as_user.php” file (CVE-2025-62423). Confidential information can be exposed externally.
Original description
The description as published by the source.
ClipBucket V5 provides open source video hosting with PHP. In version5.5.2 - #140 and earlier, a Blind SQL injection vulnerability exists in the Admin Area’s “/admin_area/login_as_user.php” file. Exploiting this vulnerability requires access privileges to the Admin Area.
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-62423 has been found in Admin Area's “/admin_area/login_as_user.php” file.
Confidential information can be exposed externally. CVSS score: 6.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Admin Area's “/admin_area/login_as_user.php” file CVE-2025-62423" on the vendor's site.
CVE-2025-62423 (Admin Area's “/admin_area/login_as_user.php” file) — CWE-89 / CVSS v3 6.7
Attack vector: remote (network-reachable) / no user interaction
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.
SQL injection (CWE-89) exists in Admin Area's “/admin_area/login_as_user.php” file.
Check the vendor advisory for the affected versions of Admin Area's “/admin_area/login_as_user.php” file.
Severity: Medium (CVSS 6.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Admin Area's “/admin_area/login_as_user.php” file を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com
- patch security-advisories@github.com