novel-plus up to 4.3.0-RC1 /novel/pay/list offset/limit/sort sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in novel-plus up to 4.3.0-RC1. Affected by this vulnerability is an unknown functionality of the file /novel/pay/list. This manipulation of the argument offset/limit/sort causes sql injection. This vulnerability appears as CVE-2024-24013. There is no available exploit.
Details
A vulnerability was found in novel-plus up to 4.3.0-RC1. It has been declared as critical. Affected by this vulnerability is an unknown code of the file /novel/pay/list. The manipulation of the argument offset/limit/sort with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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/pay/list
The weakness was presented 02/06/2024. This vulnerability is known as CVE-2024-24013 since 01/25/2024. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/25/2024 🔍02/06/2024 🔍
02/06/2024 🔍
06/12/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-24013 (🔍)
GCVE (CVE): GCVE-0-2024-24013
GCVE (VulDB): GCVE-100-253033
Entry
Created: 02/06/2024 17:55Updated: 06/12/2025 22:20
Changes: 02/06/2024 17:55 (36), 02/06/2024 17:57 (1), 03/01/2024 10:38 (1), 03/01/2024 10:44 (11), 06/12/2025 22:20 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.