dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-13479

HIGH · 7.5 CVSS v3.1 Published 2026-05-21
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 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 PosCube Hardware Software and Consulting Ltd. QR Menu allows Exploitation of Trusted Identifiers. This issue affects QR Menu: through 21052026. 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 · moderate confidence

The vulnerability is an authorization bypass where user-controlled keys (such as user IDs, session tokens, or object references in request parameters) are not properly validated, allowing attackers to manipulate these trusted identifiers to access unauthorized functionality or data. This is likely an Insecure Direct Object Reference (IDOR) or broken access control issue in the QR Menu application's backend.

MitigationImplement proper authorization checks on all sensitive operations, validate that the authenticated user has rights to access the requested resource identified by user-controlled keys, and enforce consistent access control validation throughout the application.

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

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
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? 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. Identify QR Menu installation and version
    Locate the QR Menu installation directory and check version files such as package.json, composer.json, or a version configuration file. If using a hosted instance, check the admin panel or API for version information.
    Affected if The installed version cannot be determined or falls within an affected version range.
  2. Review authorization logic for user-controlled input usage
    Examine application source code, particularly authentication and authorization modules. Search for code patterns where request parameters, headers, or user-supplied identifiers (such as user IDs, tokens, or record IDs) are used directly in access control decisions without validation.
    Affected if Authorization checks rely on values that originate from user requests without server-side validation of user permissions.
  3. Inspect API endpoints and protected routes
    Test API endpoints or application routes that should require authorization. Attempt to access protected resources by modifying identifiers in requests (such as record IDs or object references) to see if access is incorrectly granted based on manipulated values.
    Affected if Modifying user-controlled identifiers in requests grants unauthorized access to resources belonging to other users.
  4. Check authentication configuration
    Review authentication configuration files and session management code. Identify whether the system uses user-supplied values (like IDs from URL parameters or cookies) as the sole basis for granting access to protected functionality.
    Affected if Access control decisions trust user-supplied identifiers without verifying the authenticated user's actual permissions.

If the application uses user-controlled input as trusted identifiers for authorization without server-side permission validation, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all sensitive operations, validate that the authenticated user has rights to access the requested resource identified by user-controlled keys, and enforce consistent access control validation throughout the application.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13479 — 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-13479 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