LabCollector 5.423 login.php Login sql injection

Summaryinfo

A vulnerability, which was classified as critical, was found in LabCollector 5.423. Affected is an unknown function of the file login.php. Such manipulation of the argument Login leads to sql injection. This vulnerability is listed as CVE-2019-25438. The attack may be performed from remote. In addition, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in LabCollector 5.423. Affected by this issue is some unknown functionality of the file login.php. The manipulation of the argument login 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. CVE summarizes:

LabCollector 5.423 contains multiple SQL injection vulnerabilities that allow unauthenticated attackers to execute arbitrary SQL commands by injecting malicious code through POST parameters. Attackers can submit crafted SQL payloads in the login parameter of login.php or the user_name parameter of retrieve_password.php to extract sensitive database information without authentication.

The weakness was presented by Carlos Avila as 47460. The advisory is available at exploit-db.com. This vulnerability is handled as CVE-2019-25438 since 02/20/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:login.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 vulnerability database at Exploit-DB (47460). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• LabCollector

Version

• 5.423

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion