dbcve.org
Novel PlusApplication · Xxyopen

CVE-2025-4016

CRITICAL · 9.1 CVSS v3.1 Published 2025-04-28
Fix available
A fix is available. Upgrade to 5.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability classified as critical has been found in 20120630 Novel-Plus up to 0e156c04b4b7ce0563bef6c97af4476fcda8f160. This affects the function deleteIndex of the file novel-admin/src/main/java/com/java2nb/common/controller/LogController.java. The manipulation leads to improper authorization. It is possible to initiate the attack 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Novel-Plus up to the specified commit contains an improper authorization vulnerability in the deleteIndex function of LogController.java within the novel-admin module. The vulnerability allows remote attackers to bypass authorization controls and potentially delete log indices without proper authentication or authorization checks. The CVSS 9.1 score indicates critical severity with high exploitability and potential for significant data or system compromise.

MitigationImplement proper authentication and authorization checks in the deleteIndex function, ensuring users have appropriate permissions before allowing deletion operations. Alternatively, apply network-level restrictions or disable the vulnerable endpoint until an official patch is available from the vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Novel PlusApplication
Affected:< 5.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Novel-Plus installation
    Locate the Novel-Plus application deployment in your environment (typically a Java web application in a servlet container or as a standalone JAR)
    Affected if Novel-Plus is present in the environment
  2. Determine installed version
    Check the application version file, build configuration (pom.xml), or the application's runtime version display. Compare the version to the affected range of < 5.1.1
    Affected if Installed version is lower than 5.1.1
  3. Verify novel-admin module is deployed
    Check if the novel-admin module is deployed and active in the application. This module contains the vulnerable LogController.java file
    Affected if novel-admin module is present in the deployment
  4. Confirm deleteIndex endpoint exists
    Inspect the deployed LogController.java file or its compiled classes within the novel-admin module to verify the deleteIndex function is present
    Affected if The deleteIndex function exists in LogController.java without proper authorization checks

Your environment is affected if Novel-Plus version is below 5.1.1 and the novel-admin module with the vulnerable deleteIndex function is deployed and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.1.1 or later
Fixed in 5.1.1
Interim mitigation

Implement proper authentication and authorization checks in the deleteIndex function, ensuring users have appropriate permissions before allowing deletion operations. Alternatively, apply network-level restrictions or disable the vulnerable endpoint until an official patch is available from the vendor.

Recommended fix High confidence

Novel Plus 5.1.1

  1. 1. Back up the current Novel Plus database and configuration files
  2. 2. Download Novel Plus version 5.1.1 from the official repository or distribution source
  3. 3. Stop the running Novel Plus application service
  4. 4. Replace the existing application files with the version 5.1.1 files
  5. 5. Update database schema if any migration scripts are provided in the 5.1.1 release
  6. 6. Restart the Novel Plus application service
  7. 7. Verify the deleteIndex function in LogController.java is now properly authorized
  8. 8. Test that normal log operations work correctly after the upgrade
Caveat Review release notes for 5.1.1 to check for any configuration or API changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Novel Plus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data