CVE-2026-4469
Received Received - Intake
SQL Injection in itsourcecode Frozen Foods Admin Module

Publication date: 2026-03-20

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in itsourcecode Online Frozen Foods Ordering System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/admin_edit_menu_action.php. Such manipulation of the argument product_name leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-20
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-03-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
adonesevangelista online_frozen_foods_ordering_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-2026-4469 is a critical SQL injection vulnerability found in version 1.0 of the Online Frozen Foods Ordering System, specifically in the file /admin/admin_edit_menu_action.php.

The vulnerability occurs because the product_name parameter is improperly handled and directly included in SQL queries without proper input validation or sanitization.

This flaw allows attackers to inject malicious SQL code remotely, enabling unauthorized manipulation of database queries.


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to severe impacts including unauthorized database access, leakage of sensitive information, alteration or deletion of data, and potentially full control over the affected system.

Attackers can also disrupt service availability, causing denial of service conditions.

Notably, the attack can be performed remotely without requiring user authentication or authorization.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': "The vulnerability can be detected by testing the `product_name` parameter in the file `/admin/admin_edit_menu_action.php` for SQL injection. A proof-of-concept payload that causes a time delay in the database response is: product_name=CHEESE HOTDOG' AND (SELECT 5556 FROM (SELECT(SLEEP(5)))pOis) AND 'OWrk'='OWrk."}, {'type': 'paragraph', 'content': 'Automated tools like sqlmap can be used to detect and exploit this SQL injection vulnerability efficiently.'}, {'type': 'list_item', 'content': 'Use sqlmap with a command similar to: sqlmap -u "http://target/admin/admin_edit_menu_action.php?product_name=CHEESE" --risk=3 --level=5 --time-sec=5'}, {'type': 'list_item', 'content': 'Manually test the parameter by injecting the time-based payload and observing if the response is delayed by approximately 5 seconds.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
  • Implement strict input validation and filtering to ensure inputs conform to expected formats.
  • Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations.
  • Conduct regular security audits of code and systems to identify and address vulnerabilities promptly.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart