CVE-2025-10407
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-10407 is a SQL injection vulnerability in the SourceCodester Student Grading System version 1.0, specifically in the /view_user.php file. The vulnerability arises because the 'ID' parameter is not properly validated or sanitized, allowing an attacker to inject malicious SQL commands. This can be done remotely without authentication, enabling unauthorized manipulation of the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database. This can lead to unauthorized access, retrieval, modification, or deletion of sensitive data, compromising the confidentiality, integrity, and availability of your system. The exploit is publicly available and easy to use, increasing the risk of attack. [1, 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 /view_user.php endpoint with manipulated 'id' parameters to check for SQL injection vulnerabilities. One common approach is to use SQL injection testing tools or manual commands such as curl or sqlmap. For example, using curl: curl "http://target/view_user.php?id=1' OR '1'='1" to see if the response indicates SQL injection. Additionally, Google Dorking with queries like "inurl:view_user.php" can help identify vulnerable targets. Automated tools like sqlmap can be used to test the parameter: sqlmap -u "http://target/view_user.php?id=1" --batch --dbs [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include replacing or patching the affected component, specifically the /view_user.php file in SourceCodester Student Grading System 1.0, to ensure proper input validation and sanitization of the 'id' parameter. Since no known countermeasures or patches are reported, it is recommended to restrict access to the vulnerable endpoint, implement web application firewalls (WAF) to block SQL injection attempts, and consider using alternative products or updated versions that do not contain this vulnerability. Additionally, monitoring and logging suspicious activities targeting the 'id' parameter can help in early detection. [1, 2]