QAnything up to 1.1.x mysql_client.py sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.5$0-$5k0.00

Summaryinfo

A vulnerability has been found in QAnything up to 1.1.x and classified as critical. The impacted element is an unknown function of the file qanything_kernel/connector/database/mysql/mysql_client.py. The manipulation leads to sql injection. This vulnerability is listed as CVE-2024-25722. There is no available exploit. The affected component should be upgraded.

Detailsinfo

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). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Sql injection
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: QAnything 1.2.0
Patch: 35753b892c2c4361b318d68dfa3e251c85ce889c

Timelineinfo

02/11/2024 🔍
02/11/2024 +0 days 🔍
02/11/2024 +0 days 🔍
06/11/2025 +486 days 🔍

Sourcesinfo

Advisory: 35753b892c2c4361b318d68dfa3e251c85ce889c
Status: Confirmed

CVE: CVE-2024-25722 (🔍)
GCVE (CVE): GCVE-0-2024-25722
GCVE (VulDB): GCVE-100-253403
EUVD: 🔍

Entryinfo

Created: 02/11/2024 09:28
Updated: 06/11/2025 23:38
Changes: 02/11/2024 09:28 (43), 09/05/2024 15:49 (27), 06/11/2025 23:38 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!