CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in QAnything up to 1.1.x. Affected is an unknown function of the file qanything_kernel/connector/database/mysql/mysql_client.py. The manipulation leads to sql injection. This vulnerability is traded as CVE-2024-25722. There is no exploit available. It is recommended to upgrade the affected component. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in QAnything up to 1.1.x. It has been rated as critical. This issue affects an unknown part of the file qanything_kernel/connector/database/mysql/mysql_client.py. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
qanything_kernel/connector/database/mysql/mysql_client.py in qanything.ai QAnything before 1.2.0 allows SQL Injection.
The weakness was presented 02/11/2024 as 35753b892c2c4361b318d68dfa3e251c85ce889c. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-25722 since 02/11/2024. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
Upgrading to version 1.2.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 35753b892c2c4361b318d68dfa3e251c85ce889c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-23033). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
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: 🔍
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: QAnything 1.2.0
Patch: 35753b892c2c4361b318d68dfa3e251c85ce889c
Timeline
02/11/2024 🔍02/11/2024 🔍
02/11/2024 🔍
06/11/2025 🔍
Sources
Advisory: 35753b892c2c4361b318d68dfa3e251c85ce889cStatus: Confirmed
CVE: CVE-2024-25722 (🔍)
GCVE (CVE): GCVE-0-2024-25722
GCVE (VulDB): GCVE-100-253403
EUVD: 🔍
Entry
Created: 02/11/2024 09:28 AMUpdated: 06/11/2025 11:38 PM
Changes: 02/11/2024 09:28 AM (43), 09/05/2024 03:49 PM (27), 06/11/2025 11:38 PM (1)
Complete: 🔍
Cache ID: 18:B6E:40
No comments yet. Languages: en.
Please log in to comment.