CVE-2024-24014
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 versions. An attacker can pass crafted offset, limit, and sort parameters to perform SQL injection via /novel/author/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 · high confidenceSQL injection vulnerability in Novel-Plus v4.3.0-RC1 allows unauthenticated attackers to inject malicious SQL via the offset, limit, and sort parameters on the /novel/author/list endpoint. The application fails to use parameterized queries or proper input sanitization when constructing database queries for pagination and sorting operations.
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.
-
Check the installed Novel-Plus versionLocate the version file or build configuration in the application deployment directory. Common locations include version.properties, pom.xml, or the application's main JAR/WAR file metadata. Compare the version number to the affected ranges: <= 4.2.0 or = 4.3.0.Affected if The installed version is 4.3.0 (including RC1) or any version 4.2.0 and below.
-
Verify the vulnerable endpoint is exposedConfirm the /novel/author/list endpoint is accessible in the deployed application. This is typically at /novel/author/list or /api/novel/author/list depending on the configuration. Check if the application routing exposes this path without authentication requirements.Affected if The /novel/author/list endpoint is publicly accessible without authentication.
-
Identify the author list query implementationLocate the source code or decompiled classes responsible for the /novel/author/list endpoint handler. Search for the controller handling this route and examine how the offset, limit, and sort parameters are processed. Look for dynamic SQL construction using string concatenation rather than parameterized queries or ORM methods.Affected if The code uses string concatenation or unsanitized string formatting to build SQL queries with the offset, limit, or sort parameters.
-
Inspect database query loggingEnable and review database query logs or application-level SQL logging. Look for queries containing the offset, limit, or sort parameter values directly embedded in SQL statements rather than as bound parameters. Search for patterns like 'ORDER BY' with user-supplied sort values or arithmetic operations on offset/limit.Affected if Database logs show queries where offset, limit, or sort parameters appear as raw string values in SQL statements without parameter binding.
You are affected if your Novel-Plus version is 4.3.0 or <= 4.2.0, the /novel/author/list endpoint is exposed, and the code constructs SQL queries using the offset, limit, or sort parameters via string concatenation instead of parameterized queries.
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 dataReplace dynamic SQL concatenation with parameterized queries or bind variables for offset, limit, and sort parameters in the author list query. Alternatively, use the framework's ORM methods with parameterized inputs.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24014 — 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-24014 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