CVE-2025-7174
BaseFortify
Publication date: 2025-07-08
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 | library_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-7174 is a critical SQL injection vulnerability in version 1.0 of the code-projects Library System, specifically in the /teacher-issue-book.php file. The vulnerability occurs because the 'idn' parameter is improperly handled without proper input validation or sanitization, allowing attackers to inject malicious SQL code. This enables remote attackers to execute arbitrary SQL commands on the database without authentication, potentially leading to unauthorized access, data leakage, data tampering, and disruption of the system. [1, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database contents, data leakage, full system compromise, and potential service disruption. Since the exploit can be performed remotely without authentication, attackers can manipulate the database to compromise confidentiality, integrity, and availability of the system, which may lead to significant business and operational risks. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying the presence of the vulnerable file /teacher-issue-book.php and checking for the usage of the 'idn' parameter susceptible to SQL injection. One method is to use Google dorking with the query "inurl:teacher-issue-book.php" to find potentially vulnerable targets. Additionally, network or web application scanning tools can be used to test the 'idn' parameter for SQL injection by sending crafted payloads and observing responses. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible. 2) Using prepared statements in the code to ensure user inputs are treated as data and not executable SQL code. 3) Implementing strict input validation and filtering on the 'idn' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. [1, 3]