Leantime up to 2.0.14/2.1-beta2 searchUsers sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.9 | $0-$5k | 0.00 |
A vulnerability classified as critical was found in Leantime up to 2.0.14/2.1-beta2. Affected by this vulnerability is an unknown code block. The manipulation of the argument searchUsers
as part of a POST Request 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:
Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and administrators' password hashes, modify data, or drop tables. The unescaped parameter is "searchUsers" when sending a POST request to "/tickets/showKanban" with a valid session. In the code, the parameter is named "users" in class.tickets.php. This issue is fixed in versions 2.0.15 and 2.1.0 beta 3.
The weakness was shared 03/31/2020 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2020-5292 since 01/02/2020. The attack can be launched remotely. The requirement for exploitation is a single authentication. It demands that the victim is doing some kind of user interaction. 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 2.0.15 or 2.1-beta3 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.7
NVD Vector: 🔍
CNA Base Score: 8.7
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Leantime 2.0.15/2.1-beta3
Patch: github.com
Timeline
01/02/2020 🔍03/31/2020 🔍
04/01/2020 🔍
05/10/2025 🔍
Sources
Advisory: af0807f0b2c4c3c914b93f1c5d940e6b875f231fStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-5292 (🔍)
GCVE (CVE): GCVE-0-2020-5292
GCVE (VulDB): GCVE-100-152479
Entry
Created: 04/01/2020 08:35 AMUpdated: 05/10/2025 12:41 AM
Changes: 04/01/2020 08:35 AM (39), 04/01/2020 08:40 AM (11), 10/05/2020 03:25 PM (1), 05/12/2024 04:24 PM (18), 05/12/2024 04:33 PM (20), 05/10/2025 12:41 AM (7)
Complete: 🔍
Cache ID: 18:C2F:40
No comments yet. Languages: en.
Please log in to comment.