CVE-2025-15078
Unknown Unknown - Not Provided
SQL Injection in itsourcecode Student Management System /list_report.php

Publication date: 2025-12-25

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was detected in itsourcecode Student Management System 1.0. The impacted element is an unknown function of the file /list_report.php. The manipulation of the argument sy results in sql injection. The attack may be launched remotely. The exploit is now public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-25
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-12-25
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode student_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-15078 is a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the /list_report.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'sy' parameter before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling them to manipulate database queries and perform unauthorized operations such as accessing or modifying data. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and potential service disruption. Because it can be exploited remotely without authentication, it poses significant threats to system security and business continuity. [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 'sy' parameter in the /list_report.php file for SQL injection. One method is to use time-based blind SQL injection payloads, such as: sy=1' AND (SELECT 5933 FROM (SELECT(SLEEP(5)))uKqa) AND 'kqCx'='kqCx, which causes a delay in the database response if vulnerable. Additionally, the sqlmap tool can be used to automate detection with a command like: python sqlmap.py --random-agent --batch -u "http://<target_ip>:<port>/list_report.php" --data "sy=1" --dbms=mysql --current-db. Vulnerable targets can also be identified using Google dorking with the query: inurl:list_report.php. [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering (e.g., ensuring the 'sy' parameter matches expected numeric patterns), and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits should be conducted to detect and fix vulnerabilities promptly. If possible, replacing the affected product with an alternative is suggested, as no known countermeasures or patches are currently reported. [2, 3]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized access, data leakage, and data tampering, it could potentially lead to non-compliance with data protection regulations that require safeguarding sensitive information. No direct statements about compliance impact are available. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart