CVE-2020-5292: Time-based blind injection in Leantime

Published Mar 31, 2020
·
Updated

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.

Affected Software

1 affected component
Leantime Leantime<2.0.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Leantime to a version that resolves this vulnerability.

    Fixed in 2.0.15
  2. Upgrade

    Upgrade Leantime to a version that resolves this vulnerability.

    Fixed in 2.1.0 beta 3

Event History

Mar 31, 2020
CVE Published
via MITRE·06:15 PM
Data Sourced
via MITRE·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID?

The vulnerability ID is CVE-2020-5292.

2

What is the severity of CVE-2020-5292?

The severity of CVE-2020-5292 is high.

3

What is the impact of CVE-2020-5292?

The impact of CVE-2020-5292 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 administrative information.

4

How can the vulnerability in Leantime be fixed?

To fix the vulnerability in Leantime, it is recommended to upgrade to versions 2.0.15 or 2.1-beta3, which have addressed the SQL Injection vulnerability.

5

Where can I find more information about CVE-2020-5292?

More information about CVE-2020-5292 can be found in the following references: - [GitHub Commit](https://github.com/Leantime/leantime/commit/af0807f0b2c4c3c914b93f1c5d940e6b875f231f) - [GitHub Pull Request](https://github.com/Leantime/leantime/pull/181) - [GitHub Security Advisory](https://github.com/Leantime/leantime/security/advisories/GHSA-ww6x-rhvp-55hp)

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203