dbcve.org
Qr MenuApplication · Akinsoft

CVE-2025-7015

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Session Fixation vulnerability in Akın Software Computer Import Export Industry and Trade Ltd. QR Menu allows Session Fixation. This issue affects QR Menu: before s1.05.12.

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

Session Fixation vulnerability in QR Menu allows an attacker to pre-establish or manipulate a user's session ID before authentication. Upon successful login by the legitimate user, the attacker can hijack the established session by using the same fixed session ID to gain unauthorized access to the user's account. This is a critical authentication bypass vector with CVSS 9.8 indicating potential for complete compromise of user accounts.

MitigationImplement session ID regeneration upon successful authentication - invalidate the pre-login session ID and issue a new session ID after successful login. Additionally, bind sessions to additional factors like IP address or user agent, and implement session timeout policies. Upgrade to version s1.05.12 or later which contains the fix.

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
Qr MenuApplication
Affected:< s1.05.12

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. Identify if Akinsoft QR Menu is installed
    Locate the application files or check installed programs on the server. Common paths may include /var/www/, /opt/, or C:\Program Files\ on Windows servers. Look for directories or files containing 'qr menu', 'qrmenu', or 'akinsoft' in the name.
    Affected if The application is present on the system and is an Akinsoft QR Menu installation.
  2. Determine the installed version
    Check version information in the application. Look for version files, about pages within the application interface, or configuration files that may contain version strings. Compare the found version against the affected range: versions before s1.05.12 are vulnerable.
    Affected if The installed version is s1.05.11 or lower, or any version string indicating a version earlier than s1.05.12.
  3. Test session ID handling behavior
    Perform a manual test: 1) Obtain a session ID by making a request to the application before login. 2) Note the session cookie or identifier. 3) Authenticate with valid credentials while maintaining the same session ID. 4) After login, verify if the same pre-established session ID remains valid and provides authenticated access.
    Affected if The same session ID used before authentication remains valid and provides authenticated access after login without being regenerated.
  4. Review session configuration
    Examine application configuration files, session management settings, or application source code (if accessible) for how session IDs are handled during the authentication process. Look for whether session_regenerate_id() or equivalent is called after successful login.
    Affected if The application does not regenerate session IDs after authentication - the session ID persists unchanged from before to after login.

If Akinsoft QR Menu is installed and the version is earlier than s1.05.12 and session IDs are not regenerated after login, the environment is affected by this session fixation 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement session ID regeneration upon successful authentication - invalidate the pre-login session ID and issue a new session ID after successful login. Additionally, bind sessions to additional factors like IP address or user agent, and implement session timeout policies. Upgrade to version s1.05.12 or later which contains the fix.

Recommended fix High confidence

s1.05.12

  1. 1. Identify the current version of QR Menu installed in your environment
  2. 2. Create a complete backup of the QR Menu application, including database and configuration files
  3. 3. Upgrade QR Menu to version s1.05.12 or later, following the vendor's standard upgrade procedure
  4. 4. After upgrade, clear all existing user sessions to terminate any potentially hijacked sessions
  5. 5. Verify the upgrade was successful by checking the application version
  6. 6. Monitor application logs for any anomalies or session-related errors

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

Fix this in Qr Menu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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