CVE-2025-12257
BaseFortify
Publication date: 2025-10-27
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-12257 is a critical SQL injection vulnerability in the SourceCodester Online Student Result System version 1.0, specifically in the /view_result.php file. The vulnerability arises because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code remotely. This can lead to unauthorized database access, enabling attackers to retrieve, modify, or delete sensitive data without authentication. [1, 3, 4]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive student result data, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can exploit the flaw remotely without any authentication, potentially leading to loss of data integrity, confidentiality, and availability, which can disrupt business continuity and damage trust. [1, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /view_result.php endpoint with SQL injection payloads targeting the 'id' parameter. Common techniques include boolean-based blind, error-based, time-based blind, and UNION-based SQL injection tests. Tools like sqlmap can be used to automate detection and extract database information. Example commands with sqlmap: sqlmap -u "http://target/view_result.php?id=1" --batch --dbs. Manual testing can include sending HTTP GET requests with payloads such as 'id=1 AND 1=1' and 'id=1 AND 1=2' to observe differences in responses, or time-based payloads like 'id=1 AND SLEEP(5)' to detect delays indicating injection. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats (e.g., numeric only). 3) Minimizing database user permissions by avoiding use of high-privilege accounts such as root or admin for routine database operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. These steps help prevent exploitation and protect system security and data integrity. [4]