dbcve.org
Novel PlusApplication · Xxyopen

CVE-2024-24025

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to after 4.2.0 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
An arbitrary File upload vulnerability exists in Novel-Plus v4.3.0-RC1 and prior at com.java2nb.common.controller.FileController: upload(). An attacker can pass in specially crafted filename parameter to perform arbitrary File download.

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

Arbitrary file operation vulnerability in Novel-Plus v4.3.0-RC1 and prior in the FileController's upload() method. Attackers can exploit via a specially crafted filename parameter to perform unauthorized file operations (the description inconsistently mentions upload and download). The lack of proper input validation on the filename parameter enables path traversal or arbitrary file access.

MitigationImplement strict input validation and sanitization on the filename parameter, enforce proper authentication/authorization checks on file operations, and consider upgrading to a patched version if available. Restrict file operations to allowed directories and validate file types.

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:<= 4.2.0= 4.3.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 version
    Locate the application version file (typically in WEB-INF/classes/application.properties or a version manifest), or query the application's /info or /version endpoint if exposed
    Affected if Version is 4.3.0, 4.3.0-RC1, or any version <= 4.2.0
  2. Locate FileController class
    Find FileController.java in the deployed application (typically under WEB-INF/classes/com/novel/web/controller/ or in source at src/main/java/com/novel/web/controller/) and verify the upload() method exists
    Affected if FileController with upload() method is present in the application
  3. Verify FileController endpoint exposure
    Check the web.xml or Spring routing configuration to confirm the FileController endpoints (typically mapped to /file or /upload) are accessible without authentication restrictions
    Affected if FileController endpoints are publicly accessible without authentication required
  4. Inspect filename validation in upload() method
    Review the upload() method code in FileController.java to check whether the filename parameter is validated, specifically look for absence of path normalization, directory restriction, or input sanitization
    Affected if The filename parameter lacks proper validation or path traversal protection in the upload() method

A system is affected if it runs Novel-Plus version <= 4.2.0 or version 4.3.0/4.3.0-RC1 with the FileController upload endpoint exposed and without validated filename parameters.

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 a release after 4.2.0
Interim mitigation

Implement strict input validation and sanitization on the filename parameter, enforce proper authentication/authorization checks on file operations, and consider upgrading to a patched version if available. Restrict file operations to allowed directories and validate file types.

Recommended fix Moderate confidence

Novel Plus 4.3.1 or latest stable release

  1. 1. Backup the current Novel Plus application and database before making any changes.
  2. 2. Download the latest stable release of Novel Plus from the official GitHub repository (github.com/201206030/novel-plus).
  3. 3. Stop the application server running the current Novel Plus instance.
  4. 4. Deploy the new version (4.3.1 or later) to replace the vulnerable installation.
  5. 5. Verify the FileController upload functionality works correctly in the new version.
  6. 6. Restart the application server and confirm normal operation.
Caveat Review release notes for any configuration or database schema changes between versions

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 / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24025 — 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-2024-24025 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