CVE-2025-10420
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?
CVE-2025-10420 is a critical SQL injection vulnerability in the SourceCodester Student Grading System version 1.0, specifically in the /form137.php file. It occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This improper handling leads to unauthorized manipulation of database queries, enabling attackers to access, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, leakage of sensitive information, data tampering, full system compromise, and potential service disruption. Attackers can remotely exploit the flaw to manipulate or delete data, impacting the confidentiality, integrity, and availability of the system, which can severely affect 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 /form137.php file for SQL injection flaws. One approach is to use automated tools like sqlmap targeting the 'id' parameter to check for SQL injection. Additionally, Google dorking with the query "inurl:form137.php" can help identify vulnerable targets. Example sqlmap command: sqlmap -u "http://targetsite/form137.php?id=1" --batch --dbs. Monitoring for unusual database query patterns or unexpected errors related to the 'id' parameter may also help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. Enforce strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. Minimize database user permissions by avoiding high-privilege accounts such as 'root' or 'admin' for routine operations. If possible, replace the affected component with an alternative product. Conduct regular security audits to detect and address vulnerabilities promptly. [1, 3, 2]