CVE-2025-15075
SQL Injection in itsourcecode Student Management System /student_p.php
Publication date: 2025-12-25
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 |
|---|---|---|
| itsourcecode | student_management_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?
CVE-2025-15075 is a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the /student_p.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized manipulation of the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control, and potential disruption of services. Attackers can remotely execute malicious SQL commands without needing to log in, which compromises the confidentiality, integrity, and availability of the system. [2, 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 'id' parameter in the /student_p.php file for SQL injection flaws. One can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target.com/student_p.php?id=1" --batch --risk=3 --level=5. Additionally, manual testing can be done using payloads such as: id=1' AND (SELECT 2059 FROM (SELECT(SLEEP(5)))Eqbf) AND 'mJWF'='mJWF to test for time-based blind SQL injection, or UNION-based payloads with multiple columns to check for injection points. [2]
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) Enforce strict input validation and filtering, ensuring the 'id' parameter only accepts expected numeric values. 3) Minimize database user permissions by avoiding high-privilege accounts for application connections. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [2, 3]