CVE-2026-1160

7.3

PHPGurukul · Directory Management System

PHPGurukul Directory Management System 1.0 contains a remote SQL injection vulnerability in the search function of the index.php file via the searchdata argument.

Executive summary

A remote SQL injection vulnerability in PHPGurukul Directory Management System 1.0 allows unauthenticated attackers to execute arbitrary database commands, posing a significant risk to data integrity.

Vulnerability

This vulnerability is a SQL injection (CWE-89) flaw located within the search component of the index.php file. The application fails to properly sanitize the searchdata argument, allowing an unauthenticated attacker to manipulate database queries remotely.

Business impact

Successful exploitation allows unauthorized actors to access, modify, or delete sensitive information contained within the application database. Given the CVSS score of 7.3, this high-severity flaw could lead to complete compromise of the underlying data layer, potential loss of user privacy, and significant reputational damage to the organization.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the affected directory or disable the search functionality until a vendor update is released.

Proactive Monitoring: Review web server access logs for anomalous patterns in the searchdata parameter, such as SQL syntax characters (e.g., single quotes, semicolons, or comment indicators).

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to filter and block malicious SQL injection payloads targeting the searchdata argument on index.php.

Exploitation status

Public Exploit Available: Yes — a published proof-of-concept exists as documented in the GitHub issue referenced in the vulnerability report.

Analyst recommendation

This vulnerability presents a clear and immediate risk to the confidentiality and integrity of the backend database. Organizations using PHPGurukul Directory Management System 1.0 must prioritize the implementation of WAF-based filtering or disable the vulnerable search feature immediately to prevent potential data breaches while awaiting an official security update.

More PHPGurukul CVEs all →

History

  1. Disclosed CVE record published
  2. Published in the daily brief high section, carried in 2 daily briefs, Jan 20 to Jan 21
  3. Analyst report written

Sources

Originally found and disclosed by Nick_1321 (VulDB User), per the CVE Program record.