# CVE-2025-63807: Auth bypass in n/a

> Attackers can brute-force weak verification codes due to missing rate limiting, leading to account takeover via password reset.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-xqf6-9hf7-323f

## What is CVE-2025-63807?

CVE-2025-63807 is a critical authentication bypass vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts), CWE-1390 (Weak Authentication)

## Which versions are affected by CVE-2025-63807?

It affects 1 product.


Products: 2dogz Blogin.

## How do I fix CVE-2025-63807?

No fix has been published for CVE-2025-63807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63807 being exploited?

There is no known exploitation of CVE-2025-63807 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63807 and fix it if it is affected.

What it is: CVE-2025-63807 is a critical authentication bypass vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63807 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63807/ (Markdown: https://insights.sbomify.com/CVE-2025-63807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63807
- OSV: https://osv.dev/vulnerability/CVE-2025-63807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63807/
Summaries are generated and may contain mistakes; the official description above is the record.