CVE-2025-11118
BaseFortify
Publication date: 2025-09-28
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 |
|---|---|---|
| codeastro | student_grading_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11118 is a critical SQL injection vulnerability in the CodeAstro Student Grading System version 1.0, specifically in the /adminLogin.php file. The vulnerability occurs due to improper sanitization and validation of the 'staffId' parameter, which is directly used in SQL queries without proper neutralization. This allows an attacker to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, leaking or manipulating data, and even taking full control of the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on the database without authentication. This can lead to unauthorized access to sensitive data, data leakage, data manipulation or deletion, disruption of services, and potentially full system compromise. The vulnerability affects the confidentiality, integrity, and availability of the system. [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 "staffId" parameter in the /adminLogin.php file for SQL injection using time-based blind SQL injection techniques. A sample payload to test is: staffId=ad123' AND (SELECT 3833 FROM (SELECT(SLEEP(5)))QOua) AND 'cZLf'='cZLf&password=q13&login=. This payload causes a delay in the database response if the injection is successful. Additionally, the sqlmap tool can be used with a crafted HTTP POST request targeting /adminLogin.php to automate detection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. These measures help protect system security and maintain data integrity. [1, 3]