CVE-2025-8271
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
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, data tampering or deletion, full system control by attackers, and potential service interruptions. Since exploitation requires no authentication, attackers can remotely execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the affected system. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-8271 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /admin/delete_s3.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL commands remotely without authentication, potentially manipulating the database by retrieving, modifying, or deleting data. [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_s3.php endpoint for SQL injection. A proof-of-concept uses time-based blind SQL injection payloads such as 'SLEEP(5)' to confirm the vulnerability. Tools like sqlmap can be used to automate detection and enumeration of databases via this injection point. Additionally, attackers may be identified by monitoring for HTTP requests containing suspicious SQL injection payloads targeting the 'id' parameter. A Google dork query 'inurl:admin/delete_s3.php' can help identify potentially vulnerable targets externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Replace the affected component with an alternative product if possible. 5) Conduct regular security audits to detect and fix vulnerabilities promptly. [2, 3]