CVE-2025-5782
BaseFortify
Publication date: 2025-06-06
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-5782 is a critical SQL injection vulnerability in the PHPGurukul Employee Record Management System version 1.3, specifically in the /resetpassword.php file. The vulnerability occurs because the 'newpassword' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries to perform unauthorized database operations. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can exploit it remotely without authentication, making it easy to launch attacks that compromise the confidentiality, integrity, and availability of the system. [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 /resetpassword.php endpoint, specifically the 'newpassword' parameter, for SQL injection. One method is to send crafted POST requests with SQL injection payloads, such as time-based blind SQL injection payloads (e.g., using SLEEP(10)) to observe delayed responses indicating vulnerability. Additionally, Google dorking with queries like "inurl:resetpassword.php" can help identify vulnerable targets. Example command using curl to test for time-based SQL injection: curl -X POST -d "newpassword=' OR SLEEP(10)-- &confirmpassword=anything" http://target/erms/resetpassword.php Monitoring for unusual delays or errors in responses can indicate exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Replace the affected product with an alternative if possible, as no known countermeasures are documented. - Implement prepared statements with parameter binding to prevent SQL injection. - Apply strict input validation and filtering on the 'newpassword' parameter to ensure it conforms to expected formats. - Limit database user permissions to the minimum necessary to reduce impact if exploited. These measures help protect system security and maintain data integrity. [2, 3]