CVE-2024-24021
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/userFeedback/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 code via the offset, limit, and sort parameters at the /novel/userFeedback/list endpoint. User-supplied input is directly concatenated into SQL queries without proper parameterization or sanitization.
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 installed Novel-Plus versionLocate the version file or check the application metadata (such as pom.xml, version.properties, or the admin panel about page) to determine the running version of Novel-PlusAffected if The installed version is 4.3.0 or any version <= 4.2.0 (including 4.3.0-RC1)
-
Verify endpoint accessibilityConfirm that the /novel/userFeedback/list endpoint is exposed and accessible in your deployment (check your web server routing and application firewall rules)Affected if The endpoint is publicly or internally accessible without additional authentication layers beyond what the application provides
-
Test offset parameter for SQL injectionSend a crafted request to /novel/userFeedback/list with a malicious SQL payload in the offset parameter (for example: offset=1 AND 1=1--) and observe the database response or any SQL errorsAffected if The application returns unexpected database results, SQL syntax errors, or exhibits behavior indicating the input is executed as SQL code
-
Test limit parameter for SQL injectionSend a crafted request to /novel/userFeedback/list with a malicious SQL payload in the limit parameter (for example: limit=1 UNION SELECT--) and observe the database responseAffected if The application executes the injected SQL or returns data outside the intended scope
-
Test sort parameter for SQL injectionSend a crafted request to /novel/userFeedback/list with a malicious SQL payload in the sort parameter (for example: sort=id; DROP TABLE--) and observe the database responseAffected if The sort parameter input is processed as raw SQL or causes unintended database operations
Your environment is affected if you are running Novel-Plus version 4.3.0 or any version <= 4.2.0 AND the /novel/userFeedback/list endpoint is accessible without proper input sanitization or prepared statements being applied to 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 · scopedUpgrade to a patched version of Novel-Plus. Alternatively, implement prepared statements/parameterized queries for all database operations in the affected endpoint, or deploy a WAF to block SQL injection payloads until patching is possible.
Any stable release of Novel Plus beyond v4.3.0 (check GitHub releases for post-v4.3.0 versions)
- 1. Identify the current Novel Plus version in use by checking the application metadata or deployment configuration
- 2. Check the official Novel Plus GitHub repository (github.com/201206030/novel-plus) for releases newer than v4.3.0
- 3. If a stable release beyond v4.3.0 is available, plan for upgrade following standard deployment procedures
- 4. Before upgrading in production, test the new version in a staging environment to verify the SQL injection vulnerability is remediated
- 5. Alternatively, if no upgrade is immediately available, implement input validation and sanitization on the /novel/userFeedback/list endpoint parameters (offset, limit, sort) to mitigate SQL injection risk
- 6. Apply parameterized queries or prepared statements for any custom code interacting with the database related to these parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24021 — 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-24021 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