dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-0610

HIGH · 8.6 CVSS v3.1 Published 2025-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
Cross-Site Request Forgery (CSRF) vulnerability in Akınsoft QR Menü allows Cross Site Request Forgery. This issue affects QR Menü: from s1.05.06 before v1.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

Cross-Site Request Forgery (CSRF) vulnerability in Akınsoft QR Menü allows authenticated users to be tricked into executing unintended actions (such as modifying menu items or orders) via malicious requests from attacker-controlled pages. The vulnerability exists in versions s1.05.06 through versions before v1.05.12 due to missing or insufficient anti-CSRF token validation on state-changing operations.

MitigationUpgrade to Akınsoft QR Menü v1.05.12 or later, which contains the security fix. Additionally, implement anti-CSRF tokens on all state-changing operations and enable SameSite cookie attributes as a defense-in-depth measure.

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
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 the installed Akınsoft QR Menü version
    Locate the version information in the application admin panel, about page, or configuration files. Common locations include: software documentation, system information page, or the application's main configuration file.
    Affected if The version displays as s1.05.06, or any version in the range between s1.05.06 and v1.05.11 (inclusive)
  2. Compare your version to the affected range
    If version is displayed as a number (e.g., 1.05.06, 1.05.10), compare it numerically to v1.05.12. Versions below v1.05.12 are affected.
    Affected if Your installed version is 1.05.06 or higher but lower than 1.05.12
  3. Inspect state-changing operations for anti-CSRF protection
    Examine the HTML forms or API endpoints used for menu item modifications and order processing. Look for hidden input fields containing anti-CSRF tokens, or verify that the application includes CSRF tokens in request headers.
    Affected if State-changing forms (add/edit/delete menu items, process orders) lack anti-CSRF token validation or contain no token field
  4. Check cookie configuration for SameSite attributes
    Inspect the application's session cookies via browser developer tools or server configuration. Verify if SameSite attribute is set to 'Strict' or 'Lax' on authentication cookies.
    Affected if Authentication cookies lack SameSite attribute or have it set to 'None' without Secure flag

You are affected if your Akınsoft QR Menü version is s1.05.06 through any version before v1.05.12 and state-changing operations lack anti-CSRF token 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Akınsoft QR Menü v1.05.12 or later, which contains the security fix. Additionally, implement anti-CSRF tokens on all state-changing operations and enable SameSite cookie attributes as a defense-in-depth measure.

Recommended fix Moderate confidence

v1.05.12

  1. Identify the current version of Akınsoft QR Menü installed in your environment
  2. Create a full backup of the current QR Menü installation including database and configuration files
  3. Upgrade Akınsoft QR Menü to version v1.05.12 or later
  4. After upgrade, verify the new version is correctly installed
  5. Test the application to ensure core functionality works as expected after the upgrade
  6. Review application logs for any errors during and after the upgrade process
Caveat Standard upgrade; review release notes for any configuration changes if available

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-0610 — 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-0610 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