CVE-2025-45890
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 · uneditedDirectory Traversal vulnerability in novel plus before v.5.1.0 allows a remote attacker to execute arbitrary code via the filePath parameter
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 · high confidenceA directory traversal vulnerability in novel plus versions before 5.1.0 allows remote attackers to manipulate the filePath parameter to escape intended directory constraints and execute arbitrary code on the affected system.
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< 5.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Novel Plus installationSearch for Novel Plus web application files, typically deployed in Java servlet containers (Tomcat, Jetty) or check for the novel-plus WAR file or directory structure containing 'novel' in the application pathAffected if Novel Plus is deployed on the system
-
Determine installed versionCheck the application's version information - typically found in a VERSION file, pom.xml, or the WAR file's manifest. The application may also expose version details through its API endpoint or admin interfaceAffected if The version is below 5.1.0 or the version cannot be determined (unknown versions should be treated as vulnerable)
-
Verify filePath parameter is accessibleExamine the web application's routing/configuration to determine if endpoints accepting a 'filePath' parameter are publicly accessible. This typically involves URL endpoints related to file download, file serving, or file processing featuresAffected if Endpoints accepting filePath parameter are accessible without authentication or to untrusted users
-
Check for signs of exploitationReview web server access logs and application logs for suspicious patterns involving '../' sequences in filePath parameters, such as ../../etc/passwd or attempts to access WEB-INF or system directoriesAffected if Log analysis reveals path traversal attempts or unauthorized file access via filePath parameter
The environment is affected if Novel Plus version is below 5.1.0 AND the filePath parameter feature is accessible to potential attackers, allowing directory traversal to escape intended constraints.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.1.0
Upgrade to novel plus v5.1.0 or later which contains the patch for this vulnerability. Additionally, implement strict input validation on the filePath parameter to reject path traversal sequences (../, etc.) as a defense-in-depth measure.
5.1.0
- 1. Backup your current Novel Plus installation and database before proceeding with any upgrade.
- 2. Download Novel Plus version 5.1.0 or later from the official source.
- 3. Stop the Novel Plus application service.
- 4. Replace the existing installation files with the new version 5.1.0 files.
- 5. Verify file permissions are correctly set on the new installation.
- 6. Start the Novel Plus application service.
- 7. Test that the application functions normally after the upgrade.
- 8. Validate that the filePath parameter is properly sanitized and no longer permits directory traversal.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-45890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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