CVE-2025-8272
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-8272 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 application, specifically in the /admin/update_fst.php file. The vulnerability occurs because the application does not properly validate or sanitize the 'credits' parameter from user input before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, leaking or modifying data, and disrupting the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive database information, data leakage, data tampering, full system control by attackers, and potential service disruption. Since exploitation does not require user login or privileges, attackers can remotely exploit this flaw to compromise system confidentiality, integrity, and availability, threatening business continuity and security. [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_fst.php endpoint for SQL injection via the 'credits' parameter. One method is to use time-based blind SQL injection payloads, such as adding a delay using SQL commands in the 'credits' parameter to observe response time changes. For example, a proof-of-concept payload is: sname=OOJ&scode=19CS4PCOOJ&credits=4' AND (SELECT 2135 FROM (SELECT(SLEEP(5)))YgVY) AND 'MBiI'='MBiI&Update=Update Subject. Additionally, automated tools like sqlmap can be used to test the endpoint for SQL injection vulnerabilities by targeting the 'credits' parameter in POST requests. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'credits' 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) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, consider replacing the affected software with a secure alternative. [1, 3]