Thrive Smart Home 1.1 POST Parameter checklogin.php User sql injection

Summaryinfo

A vulnerability has been found in Thrive Smart Home 1.1 and classified as critical. Impacted is an unknown function of the file checklogin.php of the component POST Parameter Handler. The manipulation of the argument User leads to sql injection. This vulnerability is referenced as CVE-2019-25325. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Thrive Smart Home 1.1. This issue affects an unknown part of the file checklogin.php of the component POST Parameter Handler. The manipulation of the argument user 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:

Thrive Smart Home 1.1 contains an SQL injection vulnerability in the checklogin.php endpoint that allows unauthenticated attackers to bypass authentication by manipulating the 'user' POST parameter. Attackers can inject malicious SQL code like ' or 1=1# to manipulate login queries and gain unauthorized access to the application.

The weakness was published by Gjoko Krstic as 47814. The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2019-25325 since 02/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:checklogin.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (173728) and Exploit-DB (47814). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Thrive

Name

• Smart Home

Version

• 1.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion