# CVE-2026-90939: novel-plus through 5.3.3 Missing Authorization on the Admin /sys/user/list Endpoint

> Authenticated attackers can access the admin user list endpoint to retrieve password hashes and personal data, enabling offline cracking and account takeover.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:** 14 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m7g4-qv3h-g3h9

## What is CVE-2026-90939?

CVE-2026-90939 is a high-severity missing authorization vulnerability in 201206030 novel-plus, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

novel-plus through 5.3.3 contains an information disclosure vulnerability in the /sys/user/list endpoint that lacks proper permission annotations. Authenticated attackers can retrieve password hashes and personal data including email addresses and phone numbers for users within their data scope, enabling offline hash cracking and account takeover.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-90939 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90939 is a high-severity missing authorization vulnerability in 201206030 novel-plus, published on 14 Sep 2026. 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-2026-90939 exists.

Affected product: 201206030 novel-plus. 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-90939/ (Markdown: https://insights.sbomify.com/CVE-2026-90939/index.md)
```

## Sources

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

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