CVE-2025-9740
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL Injection in the 'id' parameter of the file log_query.php in code-projects Human Resource Integrated System 1.0. It occurs because the input is not properly validated and parameterized queries are not used, allowing an attacker to inject malicious SQL statements to manipulate database queries. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access, extraction, or modification of sensitive data within the system, potentially compromising the confidentiality, integrity, and availability of the data. [1]
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 /log_query.php file for SQL injection. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://targetsite/log_query.php?id=1" --batch. Additionally, manual testing can be done by injecting SQL syntax such as ' or '1'='1 into the 'id' parameter and observing if the application behaves unexpectedly or returns database errors. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and sanitization on the 'id' parameter in /log_query.php, and implementing parameterized queries or prepared statements to prevent SQL injection. If a patch or update is available from the vendor, apply it promptly. Additionally, restrict database permissions to limit the impact of a potential exploit and monitor logs for suspicious activity related to the 'id' parameter. [1]