# CVE-2020-35737: Missing authorization in n/a

> Attackers can modify other users' profile information by manipulating the UserIndex parameter in Newgen eGov.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 30 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rcj8-5g6r-c9cg

## What is CVE-2020-35737?

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

### Official description

In Correspondence Management System (corms) in Newgen eGov 12.0, an attacker can modify other users' profile information by manipulating the unvalidated UserIndex parameter, aka Insecure Direct Object Reference.

## Which versions are affected by CVE-2020-35737?

It affects 1 product.


Products: Newgensoft Egov.

## How do I fix CVE-2020-35737?

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

## Is CVE-2020-35737 being exploited?

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

Public exploit code:

- Newgen Correspondence Management System (corms) eGov 12.0 - IDOR (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35737 and fix it if it is affected.

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

## Sources

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

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