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

> Attackers can create unverified accounts via a legacy API, bypassing email verification controls and enabling spam or resource abuse.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-j3gq-w4jw-w88g

## What is CVE-2025-65925?

CVE-2025-65925 is a medium-severity authentication bypass vulnerability in n/a, published on 30 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 Zeroheight (SaaS) prior to 2025-06-13. A legacy user creation API pathway allowed accounts to be created without completing the intended email verification step. While unverified accounts could not access product functionality, the behavior bypassed intended verification controls and allowed unintended account creation. This could have enabled spam/fake account creation or resource usage impact. No data exposure or unauthorized access to existing accounts was reported.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Zeroheight Zeroheight.

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

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

## Is CVE-2025-65925 being exploited?

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

Public exploit code:

- Independent security finding – Zeroheight account creation bypass via missing verification enforcement (patched June 2025) (github_poc): https://github.com/Sneden/zeroheight-account-verification-bypass-CVE-2025-65925

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65925 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Dec 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-65925 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-65925/ (Markdown: https://insights.sbomify.com/CVE-2025-65925/index.md)
```

## Sources

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

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