Unauthenticated SQL injection via unsanitized editid
Published May 15, 2025 · Updated May 15, 2025
SQL injection in PHPGurukul Directory Management System 2.0 allows remote attackers to read and alter database data via editid. The edit-directory.php handler inserts the editid GET parameter directly into SQL queries without validation or parameter binding. No login is required, and crafted boolean-based, time-based, or UNION queries can disclose or alter database records.
Summary
What happened
SQL injection in PHPGurukul Directory Management System 2.0 allows remote attackers to read and alter database data via editid. The edit-directory.php handler inserts the editid GET parameter directly into SQL queries without validation or parameter binding. No login is required, and crafted boolean-based, time-based, or UNION queries can disclose or alter database records.
The record
- CVE
- CVE-2025-4697
- Published
- May 15, 2025
- Updated
- May 15, 2025
- Vendor
- PHPGurukul
- Product
- Directory Management System
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- editid SQL injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo