CVE-2025-8250
BaseFortify
Publication date: 2025-07-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 |
|---|---|---|
| code-projects | exam_form_submission | 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-8250 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /admin/update_s4.php file. It occurs due to improper handling and insufficient validation of the 'credits' parameter, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate SQL queries, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete data, and potentially gain full control over the affected system. It can also cause service disruption. Since the attack can be launched remotely without authentication, it poses a high risk to system security and data integrity. [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 'credits' parameter in the /admin/update_s4.php file for SQL injection. A time-based blind SQL injection test can be performed using a payload such as: credits=4' AND (SELECT 2135 FROM (SELECT(SLEEP(5)))YgVY) AND 'MBiI'='MBiI which causes a delay in the database response if vulnerable. Additionally, tools like sqlmap can be used to automate detection of this SQL injection vulnerability. Attackers may also identify vulnerable targets using Google dorking with the query: inurl:admin/update_s4.php. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product if possible. If replacement is not feasible, implement prepared statements with parameter binding to separate SQL code from user input, and apply strict input validation and filtering on the 'credits' parameter. Additionally, minimize database user permissions by avoiding use of high-privilege accounts for routine operations. Conduct regular security audits to detect and remediate vulnerabilities promptly. [1, 3, 2]