# CVE-2026-123676: A vulnerability has been found in xxyopen/201206030 novel up to 3.5.0.


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:** 11 Nov 2026
- **Also known as:** GHSA-cfhj-grhg-7vf3

## What is CVE-2026-123676?

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

### Official description

A vulnerability has been found in xxyopen/201206030 novel up to 3.5.0. This impacts the function BookServiceImpl.getBookContentAbout of the file src/main/java/io/github/xxyopen/novel/service/impl/BookServiceImpl.java of the component Book Content Service. Such manipulation of the argument chapterId leads to improper authorization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 966c4bdde3521dc0a165d15a2acff66ee33eaaa7. Applying a patch is advised to resolve this issue.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-123676 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123676 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-123676 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-123676/ (Markdown: https://insights.sbomify.com/CVE-2026-123676/index.md)
```

## Sources

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

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