CVE-2025-15205
SQL Injection in Student File Management System /download.php
Publication date: 2025-12-29
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 | student_file_management_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?
This vulnerability exists in the Student File Management System 1.0, specifically in the /download.php file. It involves SQL injection caused by manipulation of the 'istore_id' argument. An attacker can remotely exploit this vulnerability to execute unauthorized SQL commands on the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform SQL injection remotely, potentially leading to unauthorized access, data leakage, data modification, or disruption of the system's database operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Student File Management System can lead to unauthorized database access, sensitive data leakage, data tampering, and service disruption. Such impacts compromise the confidentiality, integrity, and availability of data, which are critical requirements under common standards and regulations like GDPR and HIPAA. Therefore, this vulnerability negatively affects compliance by exposing sensitive personal or health information to unauthorized parties and risking data integrity and availability. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'istore_id' parameter in the /download.php file for injection flaws. Tools like sqlmap can be used to automate detection by targeting the vulnerable parameter. Additionally, Google dorking queries such as 'inurl:download.php' can help identify potentially vulnerable targets. Using sqlmap, a command example would be: sqlmap -u "http://target.com/download.php?istore_id=1" --batch --dbs to test for SQL injection. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to ensure user inputs like 'istore_id' are treated as data, not executable SQL code. Enforce strict input validation and filtering, such as verifying that 'istore_id' conforms to expected numeric patterns. Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected product with an alternative solution as no known countermeasures currently exist. [1, 3]