CVE-2024-24017
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 /common/dict/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 confidenceSQL injection vulnerability in Novel-Plus v4.3.0-RC1 allows unauthenticated attackers to inject malicious SQL via the offset, limit, and sort parameters in the /common/dict/list endpoint. This critical flaw enables complete database compromise.
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 deploymentCheck if the Novel-Plus application is running in your environment by accessing the web interface, reviewing running services, or scanning for the application on its expected port (typically 8080).Affected if Novel-Plus is present in the environment
-
Determine installed versionLocate the version identifier in the application - typically found in the about page, a version endpoint, configuration files, or the application startup banner. Compare against affected versions: <= 4.2.0 or exactly 4.3.0.Affected if Version is 4.3.0 or 4.2.0 or lower
-
Verify endpoint accessibilityAttempt to access the /common/dict/list endpoint via HTTP GET request without providing authentication credentials.Affected if The endpoint responds without requiring authentication
-
Confirm vulnerable parameters acceptedSend a request to /common/dict/list with test values in the offset, limit, and sort parameters (for example, sort=test). Observe if the application accepts and processes these parameters without rejecting them.Affected if The application accepts and processes unsanitized input in offset, limit, or sort parameters
You are affected if Novel-Plus version 4.3.0 or 4.2.0 (or lower) is running AND the /common/dict/list endpoint is accessible without authentication AND it accepts 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.
dbcve · scopedApply vendor patch when available; alternatively, implement strict input validation and parameterized queries on the affected parameters to neutralize injection vectors.
Novel Plus 4.3.1 or later stable release
- 1. Identify the current Novel Plus version running in your environment
- 2. Download the fixed release of Novel Plus from the official GitHub repository
- 3. Before deploying, backup your current database and application configuration
- 4. Deploy the upgraded version (version 4.3.1 or later, or the latest stable release)
- 5. Verify the /common/dict/list endpoint no longer accepts malicious SQL input in offset, limit, or sort parameters
- 6. Confirm application functionality remains intact after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24017 — 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-24017 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