CVE-2025-10421
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-10421 is a critical SQL injection vulnerability in the SourceCodester Student Grading System version 1.0, specifically in the /update_account.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows remote attackers to inject malicious SQL code, potentially compromising the database by unauthorized access, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information. It can compromise the confidentiality, integrity, and availability of the system, potentially resulting in data leakage, data corruption, or service disruption. Attackers can remotely exploit this flaw using publicly available proof-of-concept exploits. [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 searching for the vulnerable endpoint using Google dorking with queries like "inurl:update_account.php" to identify exposed instances. Additionally, exploitation attempts can be tested using SQL injection tools such as sqlmap targeting POST requests to '/grading/update_account.php'. For example, a command using sqlmap could be: sqlmap -u "http://target/update_account.php" --data="id=1" --risk=3 --level=5 --technique=BEUSTQ --dbms=MySQL. Monitoring network traffic for suspicious SQL injection patterns or unusual POST requests to the vulnerable endpoint can 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 only expected values are accepted. Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. Conduct regular security audits to detect and address vulnerabilities promptly. If possible, consider replacing the affected product with a more secure alternative, as no known mitigations have been documented. [1, 3, 2]