CVE-2025-8233
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8233 is a critical SQL injection vulnerability in the Online Ordering System version 1.0, specifically in the /admin/user.php file. It occurs because the 'un' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, manipulating data, or disrupting the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data leakage, data tampering, deletion or modification of database contents, full system control by attackers, and potential service disruption. Since it can be exploited remotely without authentication, it poses a severe 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 'un' parameter in the /admin/user.php endpoint for SQL injection flaws. Techniques include error-based SQL injection and time-based blind SQL injection using crafted payloads. Tools like sqlmap can be used to automate detection. For example, using sqlmap with a POST request containing the 'un' parameter can confirm the vulnerability. Additionally, searching for the vulnerable URL pattern using Google dorking (e.g., "inurl:admin/user.php") can help identify affected systems. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no vendor patch is available. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the 'un' parameter to ensure only expected input is accepted. 4) Minimizing database user permissions to reduce impact if exploited. 5) Conducting regular security audits to detect and address vulnerabilities promptly. [2, 3, 1]