Security readout for executives and security teams
Plain-English summary
CVE-2026-1160 affects PHPGurukul Directory Management System 1.0. A search input can be manipulated to perform SQL injection. If the application is reachable, an attacker may access or alter database-backed information and potentially disrupt service. Public exploit information exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a high-priority application risk if the product is deployed and reachable. Public exploit disclosure increases urgency, especially for internet-facing systems. Prioritize inventory, exposure reduction, and vendor guidance review.
Technical view
The issue is in /index.php, Search component, via the searchdata argument. Sources classify it as CWE-89 SQL injection and CWE-74 injection. CVSS v2 is 7.5: network-accessible, low complexity, no authentication, with partial confidentiality, integrity, and availability impact. The affected product named is PHPGurukul Directory Management System version 1.0.
Likely exposure
Exposure is likely for organizations running PHPGurukul Directory Management System 1.0 with the search page reachable by users or the internet. Systems not running this product, not on version 1.0, or not exposing /index.php search functionality are less likely to be affected.
Exploitation context
The vulnerability is remotely reachable and public exploit information is referenced. The CVSS vector indicates no authentication is required. It is not listed as CISA KEV in the provided data, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence comes mainly from CVE/VulDB and a public GitHub issue. The affected function is not named beyond /index.php Search. No patch, workaround, or vendor advisory is identified in the provided sources. Avoid assuming impact beyond the stated SQL injection scope.
Mitigation direction
- Check PHPGurukul and CVE/VulDB records for vendor fixes or updated guidance.
- Restrict external access to the application until remediation is confirmed.
- Limit access to the search function where operationally feasible.
- Review database permissions used by the application for least privilege.
- Monitor web and database logs for suspicious search activity.
Validation and detection
- Inventory whether PHPGurukul Directory Management System is deployed.
- Confirm whether any deployed instance is version 1.0.
- Determine whether /index.php search functionality is externally reachable.
- Review logs for unusual searchdata parameter activity.
- Track vendor or advisory updates for a fixed version or workaround.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1160 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341754 | PHPGurukul Directory Management System Search index.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-341754 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #736333 | itsourcecode Directory Management System V1.0 SQL InjectionCVE reference · third-party-advisory
- https://github.com/YouSeeYouOneDayDayDe/Nick_1321_vuls/issues/2CVE reference · exploit, issue-tracking
- https://phpgurukul.com/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.