CVE-2025-11601
BaseFortify
Publication date: 2025-10-11
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 | online_student_result_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-11601 is a critical SQL injection vulnerability in the Online Student Result System 1.0, specifically in the /login.php file. The vulnerability occurs because the username parameter is used directly in SQL queries without proper input validation or sanitization, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate SQL queries to gain unauthorized database access, leak sensitive data, tamper with data, take full control of the system, and disrupt services. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, data tampering, full system compromise, and potential service disruption. Attackers can exploit this remotely without needing to log in, making it highly dangerous. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /login.php endpoint for SQL injection using tools like sqlmap. An example command is: sqlmap -u "http://<target-ip>/osrs/login.php" --data="username=admin&password=admin123" --dbs. Additionally, manual testing with payloads such as 'admin' AND 7192=7192 AND 'dHMh'='dHMh' can be used to check for boolean-based blind SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection, 2) Implementing strict input validation and filtering on the username parameter, 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations, and 4) Conducting regular security audits to detect and fix vulnerabilities promptly. [1]