CVE-2025-9741
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?
CVE-2025-9741 is a SQL injection vulnerability in the code-projects Human Resource Integrated System version 1.0, specifically in the 'id' parameter of the file login_query12.php. The parameter is not properly sanitized or neutralized, allowing an attacker to inject malicious SQL code to manipulate database queries. This can be exploited remotely without authentication, using techniques such as timing-based SQL injection (e.g., using SLEEP() functions) to infer sensitive information from the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker can remotely exploit the flaw to manipulate database queries, potentially accessing, modifying, or deleting sensitive data. Since no authentication is required, exploitation is easy and can lead to unauthorized data disclosure or disruption of services. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "id" parameter in the /login_query12.php file for SQL injection flaws. One common method is to use timing-based SQL injection tests, such as injecting payloads that include the SQL SLEEP() function to observe response delays. Additionally, scanning for the presence of the vulnerable endpoint can be done using Google dorking with queries like "inurl:login_query12.php". Specific commands to test might include using curl or sqlmap to send crafted requests to the URL with payloads like "id=1 OR SLEEP(5)--" and observing if the response time is delayed, indicating vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component (code-projects Human Resource Integrated System version 1.0) with an alternative product, as no known countermeasures or patches are currently available. Restricting access to the vulnerable endpoint and implementing web application firewalls (WAF) to detect and block SQL injection attempts may also help reduce risk temporarily. It is critical to avoid using the vulnerable version and monitor for any updates or patches from the vendor. [2]