CVE-2024-24019
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/roleDataPerm/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 and prior allows unauthenticated attackers to inject malicious SQL queries via the offset, limit, and sort parameters at the /system/roleDataPerm/list endpoint. The lack of proper input sanitization on these pagination and sorting parameters permits attackers to manipulate SQL queries and potentially extract, modify, or delete database contents.
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 the installed Novel-Plus versionCheck the application's version file, about page, or configuration metadata for the exact version number. Compare it to the affected ranges: versions 4.3.0-RC1 and prior, including all versions <= 4.2.0.Affected if The installed version is 4.3.0-RC1, 4.3.0, or any version <= 4.2.0.
-
Verify the vulnerable endpoint is accessibleAttempt to access the /system/roleDataPerm/list endpoint via HTTP GET request. This is an unauthenticated endpoint, so no login should be required to reach it.Affected if The endpoint responds with HTTP 200 or other valid response code, indicating it is exposed.
-
Inspect the offset, limit, and sort parametersSend a request to /system/roleDataPerm/list with test values in the offset, limit, and sort parameters (for example: offset=1&limit=10&sort=id). Observe whether the application accepts these parameters without sanitization or uses them directly in SQL queries.Affected if The application accepts and processes these parameters in SQL queries without proper input validation or parameterized queries.
You are affected if you are running Novel-Plus version 4.3.0-RC1 or prior AND the /system/roleDataPerm/list endpoint is accessible and processes the offset, limit, or sort parameters without SQL injection protection.
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 (v4.3.0-RC2 or later). If immediate upgrade is not feasible, implement input validation and use parameterized queries (prepared statements) for all database operations involving user-supplied offset, limit, and sort parameters, or deploy a WAF to block SQL injection attempts.
- 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-24019 — 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-24019 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