# CVE-2026-5413: Newgen OmniDocs GetWebApiConfiguration information disclosure

> Remote attackers can exploit high-complexity flaws in Newgen OmniDocs to disclose sensitive configuration data via the GetWebApiConfiguration endpoint.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-rrm6-76xm-g8j5

## What is CVE-2026-5413?

CVE-2026-5413 is a medium-severity vulnerability in Newgen OmniDocs, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Newgen OmniDocs up to 12.0.00. Affected by this vulnerability is an unknown functionality of the file /omnidocs/GetWebApiConfiguration. The manipulation of the argument connectionDetails leads to information disclosure. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitation appears to be difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-5413?


## How do I fix CVE-2026-5413?

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

## Is CVE-2026-5413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5413 and fix it if it is affected.

What it is: CVE-2026-5413 is a medium-severity vulnerability in Newgen OmniDocs, published on 2 Apr 2026. 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-2026-5413 in the wild and no public exploit code.

Affected product: Newgen OmniDocs. 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-2026-5413/ (Markdown: https://insights.sbomify.com/CVE-2026-5413/index.md)
```

## Sources

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

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