CVE-2026-1160
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in PHPGurukul Directory Management System 1.0. Impacted is an unknown function of the file /index.php of the component Search. The manipulation of the argument searchdata leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in PHPGurukul Directory Management System 1.0 allows remote attackers to inject malicious SQL queries via the searchdata parameter in the /index.php search component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm PHPGurukul Directory Management System is installedLook for the application in your web root directory. Check for the presence of index.php and typical Directory Management System files such as 'db.php', 'admin/', or 'dashboard' related files.Affected if The application is present on the server.
-
Identify the installed versionCheck for a version file, README, or footer in the application source code. Common locations include: /README.txt, /includes/version.php, or inspect the main index.php for version strings.Affected if The installed version is exactly 1.0.
-
Locate the vulnerable search componentVerify that /index.php exists and contains a search functionality. Search the source code for the 'searchdata' parameter or any search form that submits to the same page.Affected if The searchdata parameter is present in the search functionality.
-
Check if the search feature is publicly accessibleAttempt to access the search page via HTTP GET request to the index.php or identify if the search form is rendered on the homepage without authentication requirements.Affected if The search functionality is accessible without authentication.
-
Inspect SQL query handling for the searchdata parameterExamine the index.php source code to see if the searchdata parameter is directly inserted into SQL queries without parameterized queries or prepared statements. Look for SQL queries that concatenate or embed the searchdata variable directly.Affected if The searchdata parameter is used in dynamic SQL queries without sanitization or parameterization.
You are affected if PHPGurukul Directory Management System version 1.0 is installed with an accessible search feature that uses the searchdata parameter in unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries (prepared statements) and implement input validation on the searchdata parameter to prevent SQL injection attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1160 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data