# CVE-2025-4018: 20120630 Novel-Plus CrawlController.java addCrawlSource missing authentication

> Attackers can remotely access the addCrawlSource function without authentication, potentially modifying crawl sources in Novel-Plus.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-x7h4-fjrw-c922

## What is CVE-2025-4018?

CVE-2025-4018 is a medium-severity missing authorization vulnerability in Xxyopen Novel-Plus, published on 28 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in 20120630 Novel-Plus up to 0e156c04b4b7ce0563bef6c97af4476fcda8f160. This issue affects the function addCrawlSource of the file novel-crawl/src/main/java/com/java2nb/novel/controller/CrawlController.java. The manipulation leads to missing authentication. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-4018?

It affects 1 product.


Products: Xxyopen Novel-Plus.

## How do I fix CVE-2025-4018?

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

## Is CVE-2025-4018 being exploited?

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

## Other vulnerabilities in Xxyopen Novel-Plus

- [CVE-2025-45890](https://insights.sbomify.com/CVE-2025-45890/): Path traversal in n/a (critical 9.8)
- [CVE-2024-25274](https://insights.sbomify.com/CVE-2024-25274/): File upload in n/a (critical 9.8)
- [CVE-2024-24014](https://insights.sbomify.com/CVE-2024-24014/): SQL injection in n/a (critical 9.8)
- [CVE-2024-24018](https://insights.sbomify.com/CVE-2024-24018/): SQL injection in n/a (critical 9.8)
- [CVE-2024-24021](https://insights.sbomify.com/CVE-2024-24021/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4018 and fix it if it is affected.

What it is: CVE-2025-4018 is a medium-severity missing authorization vulnerability in Xxyopen Novel-Plus, published on 28 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4018 in the wild and no public exploit code.

Affected product: Xxyopen 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-2025-4018/ (Markdown: https://insights.sbomify.com/CVE-2025-4018/index.md)
```

## Sources

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

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