Drawing-Captcha APP provides interactive, engaging verification for Web-Based Applications. The vulnerability is a Host…
Summary
Vulnerability reported (CVE-2025-62428). Risk of unauthorized operations or information disclosure. Exploitable via Host header. Mitigation: upgrade to 1.2.5-alpha-patch or later.
Original description
The description as published by the source.
Drawing-Captcha APP provides interactive, engaging verification for Web-Based Applications. The vulnerability is a Host Header Injection in the /register and /confirm-email endpoints. It allows an attacker to manipulate the Host header in HTTP requests to generate malicious email confirmation links. These links can redirect users to attacker-controlled domains. This vulnerability affects all users relying on email confirmation for account registration or verification. This vulnerability is fixed in 1.2.5-alpha-patch.
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-62428 has been found.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade the affected software to 1.2.5-alpha-patch or later.
If unsure, ask your IT team or search "CVE-2025-62428" on the vendor's site.
CVE-2025-62428 — CWE-601
Attack surface: Host header
Patched: 1.2.5-alpha-patch — 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-601) has been reported. Attackers reach the vulnerable code path via Host header.
Check the vendor advisory for the affected versions. Attack surface: Host header.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.2.5-alpha-patch.
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・依存マニフェストで影響コンポーネントを特定する。
-
2Apply patch patch
Upgrade to 1.2.5-alpha-patchステージング環境で 1.2.5-alpha-patch に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。