Skip to main content

Menulux Mobile App CVE-2026-2346

| EUVDEUVD-2026-52263 CRITICAL
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-03 TR-CERT GHSA-vhg6-8gp7-pg76
9.8
CVSS 3.1 · Vendor: TR-CERT
Share

Severity by source

Vendor (TR-CERT) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.1 HIGH

CWE-639 key manipulation realistically needs an authenticated session (PR:L) and yields integrity tampering (I:H) with only incidental data exposure (C:L) and no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TR-CERT).

CVSS VectorVendor: TR-CERT

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Aug 03, 2026 - 13:20 vuln.today
CVE Published
Aug 03, 2026 - 11:49 cve.org
CRITICAL 9.8

DescriptionCVE.org

Authorization bypass through User-Controlled key vulnerability in Menulux Software Inc. Mobile App allows Software Integrity Attack.

This issue affects Mobile App: through 12.05.2026.

AnalysisAI

Authorization bypass in Menulux Software Inc. Mobile App (all versions through the 12.05.2026 build) lets remote attackers manipulate a user-controlled key (an Insecure Direct Object Reference, CWE-639) to reach or alter resources belonging to other users, enabling a software integrity attack. TR-CERT rates it CVSS 9.8 with full CIA impact, though the primary documented effect is integrity tampering. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.

Technical ContextAI

Menulux is a Turkish restaurant/hospitality platform (digital menu, ordering and POS integration) and this flaw resides in its companion Mobile App, identified by CPE cpe:2.3:a:menulux_software_inc.:mobile_app. The root cause is CWE-639, Authorization Bypass Through User-Controlled Key: the application uses a client-supplied identifier (such as a user, order, or object ID passed in an API request) to select a backend record without verifying that the requesting principal is authorized to act on that record. Because the object reference is direct and trusted, changing the key value in a request causes the server to operate on another tenant's or user's object, which the advisory characterizes as a software integrity attack.

RemediationAI

Upgrade the Menulux Mobile App to a build newer than the 12.05.2026 version once the vendor publishes a fixed release; the input data provides no exact fixed version number, so this is a patch-available-per-advisory situation rather than a confirmed tagged release - track the TR-CERT bulletin at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0729 and contact Menulux to confirm the corrected build. Until a fix is deployed, apply server-side authorization enforcement so that every request validating a user-supplied object key checks ownership/tenancy (do not rely on the client-provided ID alone); where feasible, replace direct sequential object references with unguessable/opaque tokens or per-session mappings, and add server-side access-control logging and rate limiting on the affected API endpoints to detect key-enumeration attempts. These controls are backend changes and may require vendor cooperation since the flaw is in a packaged mobile product; the trade-off is added request-validation overhead and potential integration testing against existing clients.

Share

CVE-2026-2346 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy