# CVE-2025-65427: Security feature bypass in n/a

> Attackers can brute force passwords on the Dbit N300 T1 Pro router due to missing rate limiting on the login API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-6vj9-7994-7367

## What is CVE-2025-65427?

CVE-2025-65427 is a medium-severity vulnerability in n/a, published on 16 Dec 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 Dbit N300 T1 Pro Easy Setup Wireless Wi-Fi Router on firmware version V1.0.0 does not implement rate limiting to /api/login allowing attackers to brute force password enumerations.

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

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

It affects 1 product.


Products: Dbitnet Dbit N300 T1 Pro Firmware.

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

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

## Is CVE-2025-65427 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65427 exists.

Public exploit code:

- CVE-2025-65427: Missing rate limiting in Dbit N300 T1 Pro router login API allows brute-force attacks (github_poc): https://github.com/kirubel-cve/CVE-2025-65427

## Other vulnerabilities in n/a

- [CVE-2026-36956](https://insights.sbomify.com/CVE-2026-36956/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2026-36957](https://insights.sbomify.com/CVE-2026-36957/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65427 is a medium-severity vulnerability in n/a, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65427 exists.

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-65427/ (Markdown: https://insights.sbomify.com/CVE-2025-65427/index.md)
```

## Sources

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

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