CVE-2026-123676 · Other
NO FIX YET · SEE WHAT TO DO
The xxyopen novel application up to version 3.5.0 fails to check authorization properly in BookServiceImpl.getBookContentAbout when handling the chapterId argument. A remote attacker can manipulate that argument to access book chapter content they should not be able to read.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running the xxyopen novel application up to version 3.5.0 are exposed, because chapter content is served through the affected BookServiceImpl.getBookContentAbout function. The sources do not say whether an account is needed or whether the issue depends on configuration, so exposure beyond the affected version is unknown.
Who cares java, novel, self-hosted
3.5.0 or earlier, and whether commit 966c4bdde3521dc0a165d15a2acff66ee33eaaa7 is applied to BookServiceImpl.java966c4bdde3521dc0a165d15a2acff66ee33eaaa7 from the project repositoryA 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.
This page as .md · .json · 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.