CVE-2025-10419
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-10419 is a critical SQL injection vulnerability in version 1.0 of the SourceCodester Student Grading System, specifically in the file /del_promote.php. The issue arises because the 'sy' parameter is improperly handled and directly used in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially leading to unauthorized database access, data leakage, data tampering, and even full system compromise or service disruption. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and filtering on the `sy` parameter to ensure only expected input is accepted. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, consider replacing the affected component with a secure alternative. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can remotely exploit the SQL injection flaw to access sensitive data, modify or delete data, disrupt services, or gain full control over the affected system. This can lead to data breaches, loss of trust, operational downtime, and potential financial or reputational damage. [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 `sy` parameter in POST requests to `/del_promote.php` for SQL injection. Tools like sqlmap can be used to automate detection. For example, a command to test might be: sqlmap -u "http://target/del_promote.php" --data="sy=1" --risk=3 --level=5 --batch. Additionally, searching for the vulnerable endpoint using Google dorking such as `inurl:del_promote.php` can help identify affected systems. [1, 2]