CVE-2025-5838
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-5838 is a critical SQL injection vulnerability in PHPGurukul Employee Record Management System version 1.3. It exists in the /admin/adminprofile.php file, specifically involving the AdminName parameter. This parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries and perform unauthorized database operations remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data manipulation, and potentially full system compromise or service disruption. It affects the confidentiality, integrity, and availability of the system. Attackers can exploit it remotely to manipulate or extract sensitive data and disrupt normal operations. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/adminprofile.php endpoint for SQL injection via the AdminName parameter. A time-based blind SQL injection test can be performed by sending a POST request with a payload such as: AdminName=Admin' RLIKE SLEEP(5)-- zQka to observe if the database response is delayed, indicating vulnerability. Additionally, tools like sqlmap can be used to automate detection and extract database information. Attackers may also identify vulnerable targets using Google dorking with queries like inurl:admin/adminprofile.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the AdminName parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. If possible, replace the affected component with an alternative product until a patch or fix is available. [2, 3]