# CVE-2026-123677: xxyopen/201206030 novel Book Chapter Read BookServiceImpl.java getBookChapter authorization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-m82c-2m26-vg76

## What is CVE-2026-123677?

CVE-2026-123677 is a medium-severity vulnerability in 201206030 novel, published on 6 Nov 2026. 

### Official description

A vulnerability was found in xxyopen/201206030 novel up to 3.5.0. Affected is the function getBookChapter of the file src/main/java/io/github/xxyopen/novel/service/impl/BookServiceImpl.java of the component Book Chapter Read Handler. Performing a manipulation of the argument chapterId results in authorization bypass. The attack may be initiated remotely. The exploit has been made public and could be used. The patch is named b8134e774820e0971fa9d8074405b49a01c99bdc. It is suggested to install a patch to address this issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-123677 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123677 is a medium-severity vulnerability in 201206030 novel, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123677 exists.

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

## Sources

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

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