CVE-2025-10408
BaseFortify
Publication date: 2025-09-14
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 |
|---|---|---|
| oretnom23 | student_grading_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?
CVE-2025-10408 is a critical SQL injection vulnerability in the SourceCodester Student Grading System version 1.0, specifically in the /edit_user.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially gaining unauthorized access to the database, manipulating data, or disrupting the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, deletion, and exposure of sensitive information. Attackers can gain full system control, disrupt services, and compromise business continuity. The exploit can be performed remotely without authentication, increasing the risk of exploitation. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability compromises the confidentiality, integrity, and availability of sensitive data, which can lead to violations of data protection regulations such as GDPR and HIPAA. Unauthorized access and data leakage caused by the SQL injection could result in non-compliance, legal penalties, and damage to organizational reputation. [2]
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 /edit_user.php file for SQL injection. One common approach is to use automated tools like sqlmap to test for SQL injection vulnerabilities. For example, a command to test this could be: sqlmap -u "http://target/edit_user.php?id=1" --method=POST --data="id=1" --risk=3 --level=5. Additionally, attackers can be detected by monitoring for unusual or malicious SQL queries targeting the 'id' parameter or by searching for access attempts to /edit_user.php with suspicious input. Google dorking such as searching for "inurl:edit_user.php" can help locate vulnerable targets but is not a detection method on your own network. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product as no official patch is available. [1, 2, 3]