CVE-2024-24018
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 in crafted offset, limit, and sort parameters to perform SQL injection via /system/dataPerm/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 queries via the offset, limit, and sort parameters on the /system/dataPerm/list endpoint, potentially leading to full 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.
-
Confirm Novel-Plus is deployedIdentify the application by checking running Java processes, deployed WAR files, or web server access logs for 'novel' or 'NovelPlus' path references. Check for the application's context path in the deployment descriptor (web.xml) or application server configuration.Affected if Novel-Plus is running as a Java web application on the server
-
Determine installed versionLocate the version by examining the WAR file name (e.g., novel-plus-4.x.x.war), the MANIFEST.MF file inside the deployed WAR, or the pom.xml/build.gradle if source code is available. Also check any version configuration files in the application root directory.Affected if The version number matches <= 4.2.0 or equals exactly 4.3.0
-
Verify vulnerable endpoint is exposedSend a GET request to /system/dataPerm/list (or the full path including context root, e.g., /novel-plus/system/dataPerm/list) using curl or a browser. Check if the endpoint responds with data or an HTTP 200 status code.Affected if The endpoint returns a valid response without requiring authentication (unauthenticated access is possible)
-
Test parameter acceptanceSend a request with modified parameter values: /system/dataPerm/list?offset=0&limit=10&sort=id. Observe whether the application accepts these parameters and reflects them in the response. A vulnerable application will process unsanitized input in the SQL query.Affected if The application accepts and processes the offset, limit, or sort parameters in the SQL query without sanitization
If Novel-Plus version 4.2.0 or below, or exactly 4.3.0 is installed AND the /system/dataPerm/list endpoint is accessible without authentication, the environment is vulnerable to CVE-2024-24018.
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 to a patched version of Novel-Plus. As an immediate workaround, implement strict input validation on the affected parameters and/or deploy a WAF rule to block SQL injection payloads.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24018 — 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-24018 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