# CVE-2023-43902: Auth bypass in n/a

> Unauthenticated attackers can bypass password reset controls to take over any user account, including administrators, in eMudhra emSigner.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2023
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-gp56-58fv-r42c

## What is CVE-2023-43902?

CVE-2023-43902 is a high-severity authentication bypass vulnerability in n/a, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect access control in the Forgot Your Password function of eMudhra emSigner v2.8.7 allows unauthenticated attackers to access accounts of all registered users, including those with administrator privileges via a crafted password reset token.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2023-43902?

It affects 1 product.


Products: Emudhra Emsigner.

## How do I fix CVE-2023-43902?

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

## Is CVE-2023-43902 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43902 exists.

## Other vulnerabilities in n/a

- [CVE-2023-43900](https://insights.sbomify.com/CVE-2023-43900/): Missing authorization in n/a (medium 6.5)
- [CVE-2023-43901](https://insights.sbomify.com/CVE-2023-43901/): Missing authorization in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43902 and fix it if it is affected.

What it is: CVE-2023-43902 is a high-severity authentication bypass vulnerability in n/a, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43902 exists.

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-2023-43902/ (Markdown: https://insights.sbomify.com/CVE-2023-43902/index.md)
```

## Sources

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

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