Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2026-39912 β€” AI Deep Analysis Summary

CVSS 9.1 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: V2Board/Xboard leaks auth tokens in HTTP responses. πŸ’₯ **Consequence**: Unauthenticated attackers can hijack accounts and gain full control. It's a critical data exposure flaw.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **CWE**: CWE-201 (Information Exposure Through Sent Data).…

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: V2Board versions **1.6.1 to 1.7.4**. πŸ“¦ **Also Affected**: Xboard versions **0.1.9 and earlier**. 🏒 **Vendor**: v2board / cedar2025.

Q4What can hackers do? (Privileges/Data)

πŸ”“ **Privileges**: Full account takeover. πŸ“‚ **Data**: Access to all user data, subscription configs, and panel settings. No login required for the attacker to exploit the leaked token.

Q5Is exploitation threshold high? (Auth/Config)

πŸ“‰ **Threshold**: LOW. 🚫 **Auth**: No authentication needed to trigger the vulnerability. βš™οΈ **Config**: Requires the victim to use the 'Login with Mail Link' feature, which is a standard admin/user action.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ” **Exploit Status**: Public technical descriptions exist (e.g., chocapikk.com). πŸ“ **PoC**: Specific code references provided in GitHub issues. Wild exploitation is likely possible given the low barrier.

Q7How to self-check? (Features/Scanning)

πŸ”Ž **Check**: Scan for V2Board/Xboard instances. πŸ“‘ **Test**: Trigger a `loginWithMailLink` request and inspect the HTTP response body for exposed JWT/Auth tokens. Look for sensitive data in plain text responses.

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Fixed**: Yes. PR #981 on GitHub addresses the issue. πŸ“… **Published**: Advisory released on 2026-04-09. Users should update to patched versions immediately.

Q9What if no patch? (Workaround)

πŸ›‘οΈ **Workaround**: Disable the `loginWithMailLink` feature if possible. 🚫 **Mitigation**: Implement strict response filtering to prevent token leakage. Monitor logs for unusual auth token exposures.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Priority**: CRITICAL. 🚨 **Urgency**: High. CVSS Score indicates High Confidentiality and Integrity impact. Immediate patching is required to prevent account takeovers.