CVE-2024-24023
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 · uneditedA SQL injection vulnerability exists in Novel-Plus v4.3.0-RC1 and prior. An attacker can pass specially crafted offset, limit, and sort parameters to perform SQL injection via /novel/bookContent/list.
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 confidenceA SQL injection vulnerability in Novel-Plus v4.3.0-RC1 and prior allows attackers to inject malicious SQL through the offset, limit, and sort parameters at the /novel/bookContent/list endpoint. The lack of proper input sanitization or parameterized queries on these parameters enables unauthenticated attackers to manipulate database queries.
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<= 4.2.0= 4.3.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 installationLocate the Novel-Plus application files or check running services. Common locations include /opt/novel-plus, /var/www/novel-plus, or check for Java processes running the novel application (look for novel*.jar or similar)Affected if Novel-Plus is installed and running
-
Determine installed versionCheck the application version file or banner. Common locations: version file in the application root, or check the JAR/WAR file manifest, or look for version in the application welcome page or API documentation endpointAffected if The installed version is 4.3.0-RC1, 4.3.0, 4.2.0, or any version <= 4.2.0
-
Verify vulnerable endpoint existsConfirm the /novel/bookContent/list endpoint is accessible. This is typically a REST API endpoint. Test with a basic HTTP request to this path on the serverAffected if The endpoint responds (even with an error) indicating it exists in the application
-
Check for unpatched SQL handlingReview the application logs or source code (if accessible) for the bookContent/list endpoint handler, specifically how the offset, limit, and sort parameters are processed. Look for direct string concatenation in SQL queries instead of parameterized queriesAffected if The code uses the offset, limit, or sort parameters directly in SQL queries without proper parameterization or input validation
A user is affected if they are running Novel-Plus version 4.3.0-RC1, 4.3.0, or any version <= 4.2.0 and the /novel/bookContent/list endpoint is accessible with unparameterized SQL query handling for the offset, limit, or sort parameters.
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.
From vendor dataUpgrade Novel-Plus to a patched version that addresses this vulnerability, or implement proper input validation and parameterized queries for the affected endpoint parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2024-24023 — 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-2024-24023 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