Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-13474

HIGH · 7.5 CVSS v3.1 Published 2025-12-16

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Authorization Bypass Through User-Controlled Key vulnerability in Menulux Software Inc. Mobile App allows Exploitation of Trusted Identifiers. This issue affects Mobile App: before 9.5.8.

Technical summary

dbcve analysis · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Menulux Mobile App where user-controllable keys (likely object identifiers or parameters) are used to access resources without proper authorization validation. An attacker can manipulate these trusted identifiers to bypass authentication and access unauthorized data or functionality.

MitigationUpgrade Menulux Mobile App to version 9.5.8 or later to obtain the vendor fix for this authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Menulux Mobile App installation

Check the device (iOS/Android) for the Menulux Mobile App installation. On Android, inspect installed packages for 'menulux' or similar. On iOS, check the app list for 'Menulux'.

Affected if The Menulux Mobile App is installed on any device in the environment
Determine the installed app version

On Android, go to Settings > Apps > Menulux > Version info. On iOS, go to App Store > Menulux > Version or long-press the app icon to view version. Compare against the fixed version 9.5.8.

Affected if The installed version is lower than 9.5.8 (e.g., 9.5.7, 9.5.6, etc.)
Verify app handles user-controllable identifiers

Observe app behavior during use. The IDOR vulnerability applies when the app transmits or processes user-supplied object identifiers (such as order IDs, user IDs, or record keys) to the backend without visible authorization validation.

Affected if The app is actively used and processes user-controllable keys/identifiers without documented authorization enforcement

A user is affected if the Menulux Mobile App is installed with a version lower than 9.5.8 and the app processes user-supplied identifiers that could be manipulated to access unauthorized resources.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Menulux Mobile App to version 9.5.8 or later to obtain the vendor fix for this authorization bypass vulnerability.

Recommended fix Moderate confidence

Version 9.5.8 or later

1. Identify the currently installed version of Menulux Mobile App on the device
2. For Android devices: Open Google Play Store, search for Menulux, and check for available updates; for iOS devices: Open Apple App Store and check for updates
3. If automatic updates are enabled, the app should update to version 9.5.8 or later when available
4. If manual update is required, download and install version 9.5.8 or the latest version from the official app store
5. Alternatively, if using enterprise distribution, obtain the updated .apk or .ipa from Menulux Software Inc. directly
6. After updating, verify the application version shows 9.5.8 or later in the app's about/settings section
7. Test the affected functionality to confirm normal operation and that the authorization bypass is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-13474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13474 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-13474?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-13474 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References