CVE-2025-7173
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-7173 is a critical SQL injection vulnerability in the code-projects Library System version 1.0, specifically in the /add-student.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without any authentication. [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, leading to data leakage, data tampering, and potential full system control. It can disrupt service availability and compromise the confidentiality, integrity, and availability of your system's data. Since exploitation requires no authentication and a public exploit exists, the risk of attack is high. [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 testing the /add-student.php endpoint for SQL injection via the 'username' parameter. You can use tools like sqlmap to automate detection and exploitation attempts. Example command: sqlmap -u "http://targetsite/add-student.php" --data="username=anything" --risk=3 --level=5 --batch. Additionally, Google dorking with the query "inurl:add-student.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Implementing prepared statements with parameter binding to separate SQL code from user input. 3) Applying strict input validation and filtering on the 'username' parameter. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [1, 3, 2]