CVE-2025-8239
BaseFortify
Publication date: 2025-07-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 |
|---|---|---|
| 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-8239 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 project, specifically in the /admin/ file. It occurs because the 'email' 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 manipulating database queries to gain unauthorized access or control. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, tampering with or deletion of data, full system control by attackers, and potential service interruptions. Since it can be exploited remotely without authentication, it poses a high risk to system security and data integrity. [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 /admin/ endpoint of the Exam Form Submission 1.0 application for SQL injection via the 'email' parameter. You can use tools like sqlmap or manual curl commands to inject SQL payloads and observe the responses. For example, a curl command to test might be: curl -G 'http://target/admin/' --data-urlencode "email=' OR '1'='1". Additionally, monitoring network traffic for suspicious SQL injection patterns or unexpected database errors in logs can help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements or parameterized queries to ensure user inputs like 'email' are treated as data, not executable SQL code. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for routine database operations. 4) Conducting regular security audits to identify and fix vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [1, 2]