# CVE-2025-3895: Low token entropy in MegaBIP

> An unauthenticated attacker can brute force low-entropy password reset tokens to take over user and administrator accounts in MegaBIP.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-f29p-fvxc-743q

## What is CVE-2025-3895?

CVE-2025-3895 is a critical vulnerability in Jan Syski MegaBIP, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Token used for resetting passwords in MegaBIP software are generated using a small space of random values combined with a queryable value.
 It allows an unauthenticated attacker who know user login names to brute force these tokens and change account passwords (including these belonging to administrators). 
Version 5.20 of MegaBIP fixes this issue.

Weakness: CWE-334 (Small Space of Random Values)

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


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

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

## Is CVE-2025-3895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3895 is a critical vulnerability in Jan Syski MegaBIP, published on 23 May 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-3895 in the wild and no public exploit code.

Affected product: Jan Syski MegaBIP. 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-3895/ (Markdown: https://insights.sbomify.com/CVE-2025-3895/index.md)
```

## Sources

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

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