CVE-2025-5784
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-5784 is a critical SQL injection vulnerability in version 1.3 of the PHPGurukul Employee Record Management System. It occurs in the /myexp.php file where the emp3ctc parameter is improperly sanitized and directly used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling them to manipulate database queries arbitrarily and perform unauthorized operations such as data leakage, tampering, or disruption. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leak sensitive employee or business data, alter or delete records, and potentially disrupt system availability. It threatens the confidentiality, integrity, and availability of your system and may lead to full system compromise or service disruption. [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 /myexp.php endpoint for SQL injection via the emp3ctc parameter. One approach is to use sqlmap, an automated SQL injection tool, to test the parameter. For example, a command like: sqlmap -u "http://target/myexp.php" --data="emp3ctc=test" -p emp3ctc can be used to check for injection. Additionally, Google dorking with the query "inurl:myexp.php" can help identify vulnerable targets on the internet. Manual testing with crafted payloads exploiting boolean-based blind SQL injection techniques can also confirm the vulnerability. [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 emp3ctc parameter, and restricting database user permissions to the minimum necessary to limit potential damage. Since no known countermeasures currently exist for this specific product version, it is also recommended to replace the affected product with an alternative or update to a non-vulnerable version if available. [2, 3]