# CVE-2026-106700: Missing authorization in n/a

> Any authenticated user can reset arbitrary passwords, including administrators, due to missing authorization checks in the user management endpoint.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **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:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-qq2j-vwx6-5h5f

## What is CVE-2026-106700?

CVE-2026-106700 is a high-severity missing authorization vulnerability in n/a, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ELADMIN v2.7 and earlier contains an improper access control vulnerability in the user-management endpoint PUT /api/users/resetPwd of me.zhengjie.modules.system.rest.UserController. The method lacks the method-level authorization check applied to all other user-management endpoints and performs no role-level or ownership validation in UserServiceImpl.resetPwd. Any authenticated user of any role can reset the password of arbitrary users, including the built-in administrator.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106700 is a high-severity missing authorization vulnerability in n/a, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106700 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-2026-106700/ (Markdown: https://insights.sbomify.com/CVE-2026-106700/index.md)
```

## Sources

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

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