CVE-2025-7179
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-7179 is a critical SQL injection vulnerability in the code-projects Library System version 1.0, specifically in the /add-teacher.php file. It occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, letting attackers retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, full system control by attackers, and potential service disruptions. Since exploitation requires no authentication and can be done remotely, it poses a high risk to confidentiality, integrity, and availability of the affected system. [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-teacher.php endpoint for SQL injection via the 'username' parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://targetsite/add-teacher.php" --data="username=anything" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as boolean-based blind SQL injection, error-based SQL injection, or time-based blind SQL injection by injecting crafted 'username' values and observing responses or delays. Google dorking with "inurl:add-teacher.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input. 2) Apply strict input validation and filtering on the 'username' parameter to ensure only expected data is accepted. 3) Minimize database user permissions by avoiding use of high-privilege accounts for application database access. 4) Conduct regular security audits to detect and address vulnerabilities promptly. Since no vendor patch is available, consider replacing the affected software with a secure alternative if possible. [1, 3]