CVE-2025-9902
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in AKIN Software Computer Import Export Industry and Trade Co. Ltd. QRMenu allows Privilege Abuse. This issue affects QRMenu: from 1.05.12 before Version dated 05.09.2025.
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 confidenceAKIN Software QRMenu contains an authorization bypass vulnerability where user-controlled keys can be manipulated to bypass authentication and authorization checks, leading to privilege abuse. An attacker could potentially access resources or functionality beyond their authorized privileges by manipulating these user-controlled parameters.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AKIN Software QRMenu is installedSearch for QRMenu application files, check web server directories, or review installed software lists for 'QRMenu' or 'AKIN Software' entriesAffected if The product AKIN Software QRMenu is present in the environment
-
Identify QRMenu versionCheck application files for version information in configuration files, about pages, or metadata; compare against any available version recordsAffected if Installed version falls within an affected release range (if such range becomes known)
-
Review user-controlled parameter handlingInspect application code or proxy traffic to identify endpoints that accept user-controlled keys, tokens, or identifiers used in authorization decisionsAffected if Application uses user-supplied keys or parameters directly in authorization logic without server-side validation
-
Test for authorization bypass via parameter manipulationIf you have access to the application, attempt to modify user-controlled parameters (such as IDs, tokens, or keys) in requests to access resources outside your privilege levelAffected if Modifying user-controlled parameters allows access to functionality or data beyond the current user's authorized scope
-
Check for direct object reference vulnerabilitiesReview API endpoints or application URLs for exposed internal identifiers (user IDs, record IDs, keys) that could be manipulated to access other users' resourcesAffected if Application exposes direct object references that can be manipulated to bypass authorization checks
Your environment is affected if AKIN Software QRMenu is installed and uses user-controlled keys or parameters in authorization logic without proper server-side validation, allowing privilege escalation through parameter manipulation.
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 dataImplement proper server-side authorization validation for all user-controlled keys and parameters. Ensure authorization checks cannot be bypassed through direct object reference or parameter manipulation.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9902 — 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-2025-9902 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