# CVE-2025-65742: Missing authorization in n/a

> Unauthenticated attackers can access sensitive data and take over accounts via crafted API requests in Newgen OmniDocs.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 15 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-m355-3mqc-x5qx

## What is CVE-2025-65742?

CVE-2025-65742 is a high-severity missing authorization vulnerability in n/a, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated Broken Function Level Authorization (BFLA) vulnerability in Newgen OmniDocs v11.0 allows attackers to obtain sensitive information and execute a full account takeover via a crafted API request.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Newgensoft Omnidocs.

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

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

## Is CVE-2025-65742 being exploited?

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

Public exploit code:

- Advisory for CVE-2025-65742 — Newgen OmniDocs LDAP Admin BFLA (github_poc): https://github.com/CBx216/CVE-Newgen-Software-Advisories

## Other vulnerabilities in n/a

- [CVE-2011-3645](https://insights.sbomify.com/CVE-2011-3645/): Missing authorization in n/a (high 7.5)
- [CVE-2010-0701](https://insights.sbomify.com/CVE-2010-0701/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65742 is a high-severity missing authorization vulnerability in n/a, published on 15 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-65742 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-65742/ (Markdown: https://insights.sbomify.com/CVE-2025-65742/index.md)
```

## Sources

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

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