CVE-2025-8270
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-8270 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /admin/delete_s2.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate SQL queries, leading to unauthorized database access, data leakage, data tampering, and potentially full system control or service disruption. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data. It can compromise the confidentiality, integrity, and availability of the affected system. Attackers can execute arbitrary SQL commands remotely without any authentication, potentially causing data leakage, data tampering, full system compromise, and service disruption, which poses a serious threat to system security and business continuity. [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 'id' parameter in the /admin/delete_s2.php endpoint for SQL injection. A common method is to use tools like sqlmap to automate detection and exploitation. For example, running a command such as `sqlmap -u "http://target/admin/delete_s2.php?id=1" --batch` can help identify the vulnerability. Additionally, a time-based blind SQL injection test can be performed by injecting payloads that cause delays, such as appending `id=1 AND SLEEP(5)` to observe response time delays indicating vulnerability. Google dorking can also be used to find vulnerable targets by searching `inurl:admin/delete_s2.php`. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component or application with a secure alternative if possible. 2) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 3) Applying strict input validation and filtering on the 'id' parameter to ensure only expected input formats are accepted. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [1, 3, 2]