CVE-2025-8236
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 |
|---|---|---|
| fabian | online_ordering_system | 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-8236 is a critical SQL injection vulnerability in the Online Ordering System version 1.0, specifically in the /admin/edit_product.php file. It occurs due to improper handling and inadequate validation of the 'Name' or 'MULTIPART name' parameter, which is directly used in SQL queries without proper sanitization. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling them to execute arbitrary SQL commands, access, modify, or delete database data, and potentially gain full system control. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to sensitive data, data leakage, data manipulation, and deletion. Attackers can execute arbitrary SQL commands, upload web shells for remote code execution, and potentially disrupt services. This can compromise the confidentiality, integrity, and availability of the system, resulting in loss of data, system control, and service outages. [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/edit_product.php endpoint for SQL injection via the 'name' parameter in multipart/form-data POST requests. Tools like sqlmap can be used to automate detection and exploitation attempts. Example command using sqlmap: sqlmap -u "http://target/admin/edit_product.php" --data="name=TEST" --method=POST --level=5 --risk=3 --technique=BEUSTQ. Additionally, manual testing can include sending payloads that use SQL conditions or time delays (e.g., using MySQL's RLIKE or SLEEP functions) in the 'name' parameter to observe abnormal responses or delays indicating SQL injection. Google dorking such as inurl:admin/edit_product.php can help identify vulnerable targets on the network. [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 'name' parameter to ensure it conforms to expected formats and disallow malicious input. 3) Minimize database user permissions by avoiding high-privilege accounts for routine database operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected software with a secure alternative. Additionally, monitor for any signs of exploitation such as unexpected database changes or web shell uploads. [2, 3]