CVE-2026-1160
SQL Injection in PHPGurukul Directory Management System Search Component
Publication date: 2026-01-19
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | directory_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1160 is a critical SQL injection vulnerability in PHPGurukul Directory Management System version 1.0, specifically in the Search component within the /index.php file. It occurs because the 'searchdata' parameter is used directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, modification, deletion, or full system control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, modification or deletion of data, full system compromise, and potential service disruption. Since exploitation does not require authentication, attackers can remotely execute malicious SQL queries to manipulate or extract data, potentially leading to loss of confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'searchdata' parameter in the /dms/index.php file for SQL injection flaws. One method is to use automated tools like sqlmap to test for SQL injection by targeting the 'searchdata' POST parameter. Additionally, time-based blind SQL injection payloads can be used to confirm the vulnerability by injecting queries that cause the database to delay responses. Attackers may also use UNION SELECT statements with hexadecimal-encoded strings to extract data. Google dorking with queries such as "inurl:index.php" can help identify potentially vulnerable targets. Example command using sqlmap: sqlmap -u "http://target/dms/index.php" --data="searchdata=test" --technique=T --batch [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, thereby preventing SQL injection. Enforce strict input validation and filtering to ensure inputs conform to expected formats. Minimize database user permissions by avoiding high-privilege accounts such as 'root' or 'admin' for routine operations. Conduct regular security audits to detect and address vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access, modification, or deletion of sensitive data through SQL injection, it could potentially lead to violations of data protection requirements under such regulations if exploited. No direct statements about compliance impact or remediation in the context of these standards are given. [1, 2, 3]