CVE-2026-4470
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in itsourcecode Online Frozen Foods Ordering System 1.0. Affected by this issue is some unknown functionality of the file /admin/admin_edit_menu.php. Performing a manipulation of the argument product_name results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SQL injection vulnerability exists in the itsourcecode Online Frozen Foods Ordering System 1.0 within the /admin/admin_edit_menu.php file. The product_name parameter is not properly sanitized, allowing remote attackers to inject malicious SQL commands. This is a critical unauthenticated SQL injection affecting a remote production system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is installedCheck your web server document root for the presence of the Online Frozen Foods Ordering System. Look for directories containing 'admin', 'admin_edit_menu.php', or files with 'frozen' or 'foods' in the name.Affected if The Online Frozen Foods Ordering System from itsourcecode or adonesevangelista is present on the server
-
Verify the product versionCheck any version file, README, or about page within the application for the version number. Compare against version 1.0.Affected if The installed version is exactly 1.0
-
Confirm the vulnerable file existsLocate the file /admin/admin_edit_menu.php within the web application directory. This is the specific file containing the SQL injection vulnerability.Affected if The file /admin/admin_edit_menu.php exists in the web root
-
Check if the vulnerable endpoint is accessible without authenticationAttempt to access the /admin/admin_edit_menu.php page directly via HTTP request without providing any admin credentials. This is an unauthenticated vulnerability.Affected if The page loads or responds without requiring login credentials
-
Identify the vulnerable parameterExamine the admin_edit_menu.php file for the product_name parameter usage. The SQL injection occurs when this parameter is passed to a dynamic SQL query without proper sanitization.Affected if The code contains a SQL query using the product_name parameter without prepared statements or parameterized queries
If the system is running version 1.0 of the Online Frozen Foods Ordering System and the /admin/admin_edit_menu.php file is accessible without authentication, the environment is affected by CVE-2026-4470.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements in admin_edit_menu.php to properly sanitize the product_name parameter. Additionally, implement input validation, apply least-privilege database accounts, and consider deploying a WAF as a defense-in-depth measure.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data