CVE-2025-8273
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? :
Exploiting this vulnerability can lead to unauthorized database access, allowing attackers to extract sensitive information, modify or delete records, gain full control over the system, and disrupt service availability. This poses significant risks to system security, data integrity, and business continuity. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-8273 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 project, specifically in the /admin/update_s8.php file. The vulnerability occurs because the 'credits' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating database queries to extract, modify, or delete 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 /admin/update_s8.php endpoint for SQL injection via the 'credits' parameter. A proof-of-concept payload uses a time-based blind SQL injection to cause a delay in the database response, for example: `credits=4' AND (SELECT 2135 FROM (SELECT(SLEEP(5)))YgVY) AND 'MBiI'='MBiI`. You can use tools like sqlmap to automate detection by targeting the 'credits' parameter on the vulnerable URL. Additionally, Google dorking with queries like `inurl:admin/update_s8.php` can help identify potentially vulnerable instances. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'credits' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Conducting regular security audits of the code and system is also recommended. If possible, consider replacing the affected software with a secure alternative. [1, 3]