CVE-2025-9743
BaseFortify
Publication date: 2025-08-31
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 |
|---|---|---|
| code-projects | human_resource_integrated_system | 1.0 |
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?
This vulnerability is a SQL Injection flaw in the code-projects Human Resource Integrated System version 1.0, specifically in the file login_attendance2.php. It occurs because the input parameters employee_id and date are not properly sanitized or parameterized, allowing an attacker to inject malicious SQL code. This enables the attacker to manipulate database queries remotely without authentication, potentially extracting or altering data using time-based or error-based SQL injection techniques. [1, 2]
How can this vulnerability impact me? :
The vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker can remotely exploit this flaw to extract sensitive data, modify database contents, or disrupt system operations. Since no authentication is required, exploitation is easy and can lead to unauthorized access and manipulation of critical HR data. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file login_attendance2.php and testing the parameters employee_id and date for SQL injection. Attackers may use Google dorking with queries like inurl:login_attendance2.php to identify vulnerable targets. To test on your system, you can use SQL injection testing tools or manual commands such as sending crafted HTTP requests with SQL payloads to the employee_id or date parameters and observing the response for SQL errors or time delays. For example, using curl: curl 'http://target/login_attendance2.php?employee_id=1' OR '1'='1&date=2025-01-01' or using sqlmap to automate detection: sqlmap -u "http://target/login_attendance2.php?employee_id=1&date=2025-01-01" --batch [2, 1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations are currently available for this vulnerability. The recommended immediate step is to replace the affected component (code-projects Human Resource Integrated System version 1.0) with an alternative product that is not vulnerable. Additionally, restricting access to the vulnerable endpoint and monitoring for exploitation attempts may help reduce risk until a fix or replacement is implemented. [2]