CVE-2025-62771 Cross-site request forgery in M6a
High 7.5
Published
Updated
Check this codebase for CVE-2025-62771 and fix it if it is affected.
What it is: CVE-2025-62771 is a high-severity vulnerability in Mercku M6a, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62771 exists.
Affected product: Mercku M6a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-62771/ (Markdown: https://insights.sbomify.com/CVE-2025-62771/index.md)
Attackers can change passwords on Mercku M6a devices via intranet CSRF attacks, potentially taking over accounts.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-62771?
CVE-2025-62771 is a high-severity vulnerability in Mercku M6a, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Mercku M6a devices through 2.1.0 allow password changes via intranet CSRF attacks.
Weakness: CWE-352
Which versions are affected by CVE-2025-62771?
How do I fix CVE-2025-62771?
No fix has been published for CVE-2025-62771 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-62771 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62771 exists.
Sources
Also known as GHSA-j979-3w8f-32rw.