CVE-2025-10418
BaseFortify
Publication date: 2025-09-15
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?
This vulnerability is a SQL injection flaw in the SourceCodester Student Grading System version 1.0, specifically in the /view_students.php file. It occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, potentially manipulating the database in unauthorized ways. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data tampering, deletion, and exposure of sensitive information. It can also result in full system control by attackers and potential service disruption, severely compromising 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 '/view_students.php' endpoint for SQL injection via the 'id' parameter. Tools like sqlmap can be used to automate detection by sending crafted requests to the URL, for example: sqlmap -u "http://target/view_students.php?id=1" --batch. Additionally, manual testing using POST requests targeting '/grading/view_students.php' with manipulated 'id' values can reveal the vulnerability. Google Dorking with queries like 'inurl:view_students.php' can help identify potentially vulnerable instances on the network. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'id' parameter, and minimizing database user privileges by avoiding use of high-privilege accounts for routine operations. Conducting regular security audits to detect and address vulnerabilities promptly is also recommended. If possible, replacing the affected component with a secure alternative is advised since no known countermeasures are currently available. [1, 2, 3]