dbcve.org
Menu PanelApplication · Qrmenumpro

CVE-2025-7013

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-29
Fix available
A fix is available. Upgrade to after 29012026 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Authorization Bypass Through User-Controlled Key vulnerability in QR Menu Pro Smart Menu Systems Menu Panel allows Exploitation of Trusted Identifiers. This issue affects Menu Panel: through 29012026.  NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

This is an authorization bypass vulnerability where the Menu Panel in QR Menu Pro Smart Menu Systems trusts user-controlled identifiers (such as parameters or keys) to make authorization decisions without proper validation. An attacker can manipulate these trusted identifiers to bypass authentication and access unauthorized menu panel functions or data. The CVSS 9.8 indicates this is remotely exploitable with trivial attack complexity.

MitigationRestrict network exposure of the Menu Panel to trusted networks only, implement proper server-side authorization checks using indirect object references, and validate all user-supplied identifiers against the authenticated user's permissions before granting access.

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
Menu PanelApplication
Affected:<= 29012026

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.

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 checks

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

  1. Confirm QR Menu Pro installation
    Locate the QR Menu Pro Menu Panel application in your environment. Check for installed files, web root directories, or container images containing 'qrmenumpro' or 'menu panel' components.
    Affected if QR Menu Pro Menu Panel is present in the environment
  2. Identify the installed version
    Check the application's version information. This may be visible in a configuration file, about page, or metadata. Common locations include version.php, package.json, or the admin dashboard.
    Affected if The version number is 29012026 or earlier (less than or equal to 29012026)
  3. Verify Menu Panel network exposure
    Determine if the Menu Panel is accessible over the network. Check firewall rules, reverse proxy configurations, and listen addresses. Attempt to access the Menu Panel interface from an untrusted network segment if authorized.
    Affected if The Menu Panel is reachable from network segments outside the trusted internal network
  4. Inspect authorization logic for user-controlled parameters
    Review application code or configuration to identify endpoints that process user-supplied identifiers (such as ID parameters in URL paths or request bodies) for authorization decisions. Look for patterns where client values are used directly in access control checks.
    Affected if The application uses client-supplied identifiers (IDs, keys, or similar parameters) to determine access to resources without validating ownership or permissions

You are affected if QR Menu Pro Menu Panel version 29012026 or earlier is installed and its endpoints use user-supplied identifiers for authorization without proper validation.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 29012026
Interim mitigation

Restrict network exposure of the Menu Panel to trusted networks only, implement proper server-side authorization checks using indirect object references, and validate all user-supplied identifiers against the authenticated user's permissions before granting access.

Recommended fix Low confidence
  1. Isolate the affected Menu Panel system from untrusted networks immediately since no vendor patch is available
  2. Review application logs for any unauthorized access attempts using manipulated object identifiers
  3. Implement network-level segmentation to limit exposure
  4. If possible, disable the Menu Panel until a vendor response is received or alternative solution is found
  5. Monitor usom.gov.tr and siberguvenlik.gov.tr for any future vendor advisories or patches
  6. Consider implementing WAF rules to detect and block suspicious parameter tampering targeting object references

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

Fix this in Menu Panel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7013 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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