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

CVE-2025-62771

HIGH · 7.5 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Mercku M6a devices through 2.1.0 allow password changes via intranet CSRF attacks.

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

CSRF vulnerability in Mercku M6a devices through version 2.1.0 allows authenticated users on the intranet to be tricked into changing their passwords via malicious crafted requests without their consent.

MitigationImplement anti-CSRF tokens or SameSite cookie attributes for the password change functionality and all state-changing operations; release firmware update 2.1.1 or later to patch the vulnerability.

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/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 Mercku M6a device model
    Access the device web interface or check the device label/marketing materials to confirm the model is Mercku M6a
    Affected if The device is not a Mercku M6a model
  2. Check firmware version
    Log into the device web interface and navigate to System Settings or Status page to view the firmware version number
    Affected if Firmware version is 2.1.0 or earlier (versions 2.1.1 and later are patched)
  3. Verify password change endpoint lacks CSRF token
    Use a browser dev tool or HTTP proxy to capture a password change request. Inspect the request parameters for a CSRF token or anti-CSRF token field
    Affected if No CSRF token parameter is present in the password change POST request
  4. Check SameSite cookie attribute on session cookies
    Capture HTTP responses from the device web interface and examine the Set-Cookie headers for session-related cookies
    Affected if Session cookies are missing SameSite attribute or set to SameSite=None without Secure flag
  5. Confirm device is accessible on intranet
    Verify the device is accessible from the internal network without authentication barriers (e.g., same LAN/Wi-Fi network)
    Affected if Device admin interface is reachable from the intranet without additional authentication

User is affected if they have a Mercku M6a device running firmware version 2.1.0 or earlier where the password change function lacks CSRF token protection and the device is accessible from the internal network.

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 anti-CSRF tokens or SameSite cookie attributes for the password change functionality and all state-changing operations; release firmware update 2.1.1 or later to patch the vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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