CVE-2025-15034
BaseFortify
Publication date: 2025-12-23
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 |
|---|---|---|
| angeljudesuarez | student_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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows unauthorized access and manipulation of sensitive data, which can lead to breaches of confidentiality, integrity, and availability of personal or protected information. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could cause violations of these standards and regulations, potentially leading to legal and financial consequences. [1, 2]
Can you explain this vulnerability to me?
CVE-2025-15034 is a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the /record.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter received via HTTP GET requests. This allows an attacker to inject malicious SQL code remotely without authentication, enabling unauthorized manipulation of SQL queries. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise. Attackers can manipulate SQL queries to access sensitive information, disrupt service availability, and threaten 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 /record.php file for SQL injection flaws. One common approach is to use automated tools like sqlmap to test the URL for injection points. For example, you can run a command such as: sqlmap -u "http://target/record.php?id=1" --batch --level=5 --risk=3 to detect SQL injection. Additionally, manual testing can be done by injecting payloads like 'id=1' AND (SELECT SLEEP(5))-- to check for time-based blind SQL injection. Using Google dorking with the query "inurl:record.php" can help identify potentially vulnerable targets on your network or externally. [1, 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, preventing injection. 2) Enforce strict input validation and filtering, such as ensuring the 'id' parameter is numeric. 3) Minimize database user permissions by avoiding use of high-privilege accounts like 'root' or 'admin' for routine database operations. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [1, 2]