CVE-2025-15077
SQL Injection in itsourcecode Student Management System /form137.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-15077 is a critical SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the /form137.php file. The vulnerability occurs because the 'ID' parameter is not properly sanitized or validated before being used in SQL queries. This allows remote attackers to inject malicious SQL code without authentication, potentially manipulating the database queries to access, alter, or disrupt data and system operations. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and potential service disruption. This threatens the confidentiality, integrity, and availability of the system, impacting system security and business continuity. [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 'id' parameter in the /form137.php file for SQL injection. One method is to use sqlmap with a command like: python sqlmap.py --random-agent --batch -u "http://<target>/form137.php?id=1" --dbms=mysql --current-db. Additionally, Google dorking can help identify vulnerable targets using the query: inurl:form137.php. Example payloads for manual testing include time-based blind SQL injection payloads such as: id=1' AND (SELECT 8897 FROM (SELECT(SLEEP(5)))pXNc) AND 'efVL'='efVL and UNION-based SQL injection payloads like: id=1' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x716b626a71,0x41435368716c4a6d4763744d4949494f71744e64484e7246764f687462765876455a645a52656a4e,0x71707a7871),NULL,NULL,NULL,NULL-- - [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements and parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering to ensure parameters conform to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replacing the affected product with a secure alternative is recommended as no known countermeasures are reported. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access and manipulation of sensitive data through SQL injection, which can lead to data breaches and compromise confidentiality, integrity, and availability of personal or sensitive information. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal data against unauthorized access and ensuring data integrity and availability. Therefore, exploitation of this vulnerability could negatively impact compliance with these standards by exposing sensitive data and failing to protect it adequately. [1, 2, 3]