CVE-2018-25189
Received Received - Intake
SQL Injection in Data Center Audit 2.6.2 Enables Data Exposure

Publication date: 2026-03-06

Last updated on: 2026-03-06

Assigner: VulnCheck

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-06
Last Modified
2026-03-06
Generated
2026-06-16
AI Q&A
2026-03-06
EPSS Evaluated
2026-06-14
NVD
CVE-2018-25189
EUVD
EUVD-2018-21642
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2018-25189 is a high-severity SQL injection vulnerability found in Data Center Audit version 2.6.2 and earlier. It exists in the username parameter of the dca_login.php script, where the application fails to properly sanitize input. This flaw allows unauthenticated attackers to inject arbitrary SQL queries by sending crafted POST requests.

Exploitation of this vulnerability enables attackers to extract sensitive database information such as usernames, database names, and version details.

Impact Analysis

This vulnerability can have serious impacts as it allows unauthenticated attackers to execute arbitrary SQL queries on the database. Attackers can extract sensitive information including usernames, database names, and version details.

Such unauthorized data extraction can lead to data breaches, exposure of confidential information, and potential further exploitation of the system.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending crafted POST requests to the dca_login.php script targeting the username parameter with SQL injection payloads.'}, {'type': 'paragraph', 'content': 'A common detection method involves using tools like curl or specialized vulnerability scanners to submit SQL injection test payloads and observe the responses for database error messages or extracted data.'}, {'type': 'list_item', 'content': 'Example curl command to test for SQL injection in the username parameter:'}, {'type': 'list_item', 'content': 'curl -X POST -d "username=\' OR 1=1-- &password=any" http://target/dca_login.php'}, {'type': 'list_item', 'content': 'More advanced payloads can be crafted based on the proof-of-concept from ExploitDB, such as using nested SELECT statements to extract database information.'}] [2]

Mitigation Strategies

Immediate mitigation steps include restricting access to the vulnerable dca_login.php script and applying input validation or sanitization on the username parameter to prevent SQL injection.

If possible, upgrade to a fixed or newer version of Data Center Audit that addresses this vulnerability.

Additionally, consider implementing web application firewalls (WAFs) to detect and block malicious SQL injection attempts.

Monitoring logs for suspicious POST requests targeting the username parameter can also help in early detection and response.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2018-25189. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart