Data Center Audit 2.6.2 dca_login.php sql injection

Summaryinfo

A vulnerability was found in Data Center Audit 2.6.2 and classified as critical. The impacted element is an unknown function of the file dca_login.php. Executing a manipulation can lead to sql injection. The identification of this vulnerability is CVE-2018-25189. The attack may be launched remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as critical was found in Data Center Audit 2.6.2. This vulnerability affects an unknown code of the file dca_login.php. The manipulation with an unknown input 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. CVE summarizes:

Data Center Audit 2.6.2 contains an SQL injection vulnerability in the username parameter of dca_login.php that allows unauthenticated attackers to execute arbitrary SQL queries. Attackers can submit crafted SQL payloads through POST requests to extract sensitive database information including usernames, database names, and version details.

The weakness was shared by Ihsan Sencan as 45807. The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2018-25189 since 03/06/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:dca_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 databases at Exploit-DB (45807) and EUVD (EUVD-2018-21642). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Data Center Audit

Version

• 2.6.2

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion