CVE-2025-8165
BaseFortify
Publication date: 2025-07-25
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 |
|---|---|---|
| carmelo | food_ordering_review_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-8165 is a critical SQL injection vulnerability in the Food Review System 1.0, specifically in the /admin/approve_reservation.php file. It arises because the 'occasion' parameter is improperly handled without input validation or sanitization, allowing attackers to inject malicious SQL commands. This enables remote attackers to manipulate the database queries, potentially executing arbitrary SQL commands and gaining unauthorized access to sensitive data. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to sensitive information stored in the server's database, compromising confidentiality, integrity, and availability of the system. Attackers can execute arbitrary SQL commands remotely without authentication, potentially altering or deleting data, disrupting services, or gaining further access to the system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file /admin/approve_reservation.php and testing the 'occasion' parameter for SQL injection. One method is to use Google dorking with the query "inurl:admin/approve_reservation.php" to identify potentially vulnerable targets. For direct testing, you can use tools like sqlmap to test the parameter, for example: sqlmap -u "http://target/admin/approve_reservation.php?occasion=test" --batch. Additionally, manual testing by injecting SQL payloads into the 'occasion' parameter and observing the response can help detect the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component with an alternative product, as no known mitigations or countermeasures have been documented. Additionally, restricting access to the /admin/approve_reservation.php file, applying web application firewall (WAF) rules to detect and block SQL injection attempts, and disabling or limiting remote access to the vulnerable endpoint can help reduce risk until a secure fix or patch is available. [2]