Unauthenticated SQL injection via unsanitized emp1name
Published May 26, 2025 · Updated May 27, 2025
SQL injection in PHPGurukul Employee Record Management System 1.3 allows remote attackers to read or modify database data. The /admin/editempexp.php handler places the POST emp1name value directly into an SQL query without validation or sanitization. No authentication is required, and a time-based blind payload can infer database contents or delay query execution.
Summary
What happened
SQL injection in PHPGurukul Employee Record Management System 1.3 allows remote attackers to read or modify database data. The /admin/editempexp.php handler places the POST emp1name value directly into an SQL query without validation or sanitization. No authentication is required, and a time-based blind payload can infer database contents or delay query execution.
The record
- CVE
- CVE-2025-5212
- Published
- May 26, 2025
- Updated
- May 27, 2025
- Vendor
- PHPGurukul
- Product
- Employee Record Management System (ERMS)
- Classifications
- CWE-89, CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2025CVE publishedPublication date reported by the CVE source.
- May 27, 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=1.3
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
- Time-based blind emp1name 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