CVE-2025-5837
BaseFortify
Publication date: 2025-06-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | employee_record_management_system | 1.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-5837 is a critical SQL injection vulnerability in the PHPGurukul Employee Record Management System version 1.3, specifically in the /admin/allemployees.php file. The vulnerability occurs because the 'delid' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL commands remotely without authentication, potentially manipulating the database in unauthorized ways such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can exploit it to perform unauthorized database operations, including data leakage, data manipulation, and potentially full system compromise or service disruption. Since the exploit is remotely executable without authentication and publicly available, it poses a significant risk to affected systems. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the "delid" parameter in the /admin/allemployees.php file for SQL injection. One method is to use sqlmap, an automated SQL injection tool, to test the endpoint. For example, you can run: sqlmap -u "http://target/erms/admin/allemployees.php?delid=15" --risk=3 --level=5. Additionally, a time-based blind SQL injection payload such as delid=15' AND (SELECT 5700 FROM (SELECT(SLEEP(5)))sSKJ)-- GhPb can be used to confirm the vulnerability by observing response delays. Vulnerable targets can also be identified using Google dorking with the query: inurl:admin/allemployees.php. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Employing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats and block malicious data. 3) Minimizing database user privileges by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations. Since no known countermeasures or patches are currently available, replacing the vulnerable product with an alternative is also suggested. [1, 3]