Skip to main content
VulnerabilityPublished Updated

CVE-2024-24014: Novel-Plus · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHub201206030/novel-pluspkg:github/201206030/novel-plusOther threatsAffected
  • <=4.3.0-RC1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate patching: Organizations should monitor for official patches or updates from the Novel-Plus maintainers and apply them promptly once available.
  2. Input validation and sanitization: Until patches are available, implement web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the offset, limit, and sort parameters.
  3. Principle of least privilege: Restrict database user permissions used by Novel-Plus to only necessary operations, minimizing the impact of potential exploitation.
  4. Network segmentation: Isolate the application and its database from critical internal networks to limit lateral movement if compromised.
  5. Monitoring and logging: Enable detailed logging of web requests and database queries to detect suspicious activity indicative of SQL injection attempts.
  6. Code review and hardening: If source code access is available, review and refactor the handling of user inputs in the affected endpoint to ensure proper parameterization and use of prepared statements.
  7. Incident response readiness: Prepare for potential incident handling by backing up data securely and having a response plan for data breaches or service disruptions.

Description

A 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

References

Community reviews

Loading reviews…