CVE-2025-63807: Weak Authentication
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-63807, organizations should implement the following specific measures: 1) Replace the weak verification code generation mechanism with a cryptographically secure random code generator that produces sufficiently long and unpredictable codes. 2) Enforce strict rate limiting on verification code submission attempts per IP address, user account, or session to prevent brute-force attacks. 3) Introduce account lockout policies or progressive delays after multiple failed verification attempts to further deter automated guessing. 4) Implement multi-factor authentication (MFA) to reduce reliance on verification codes alone for sensitive operations like password resets. 5) Monitor authentication logs for unusual patterns indicative of brute-force attempts and set up alerts for rapid response. 6) Conduct thorough code reviews and security testing on all authentication-related components to identify and remediate similar weaknesses. 7) Engage with the software vendor or community to obtain patches or updates addressing this vulnerability once available. 8) Educate users and administrators about the risks and signs of account compromise. These targeted actions go beyond generic advice by focusing on the specific weaknesses identified in this vulnerability.
Description
An issue was discovered in weijiang1994 university-bbs (aka Blogin) in commit 9e06bab430bfc729f27b4284ba7570db3b11ce84 (2025-01-13). A weak verification code generation mechanism combined with missing rate limiting allows attackers to perform brute-force attacks on verification codes without authentication. Successful exploitation may result in account takeover via password reset or other authentication bypass methods.