dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-57197

MEDIUM · 6.0 CVSS v3.1 Published 2025-09-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
In the Payeer Android application 2.5.0, an improper access control vulnerability exists in the authentication flow for the PIN change feature. A local attacker with root access to the device can dynamically instrument the app to bypass the current PIN verification check and directly modify the authentication PIN. This allows unauthorized users to change PIN without knowing the original/current PIN.

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

The Payeer Android app version 2.5.0 contains an improper access control vulnerability in the PIN change feature. The app fails to properly validate the current PIN before allowing modification, enabling a local attacker with root access to bypass authentication through dynamic instrumentation and change the PIN without knowing the original.

MitigationThe fix requires implementing proper server-side validation of the current PIN before accepting changes, combined with secure client-side authentication checks. Additional hardening such as root detection, code obfuscation, and tamper detection should be considered to impede dynamic instrumentation attacks.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Payeer Android app is installed
    Check installed packages using 'adb shell pm list packages | grep payeer' or view installed apps in device settings
    Affected if Payeer app is present on the device
  2. Check installed Payeer app version
    Use 'adb shell dumpsys package com.payeer.app | grep versionName' or check in Android Settings > Apps > Payeer > Version
    Affected if Version is 2.5.0 or earlier (vulnerable versions)
  3. Check device root status
    Run root checker apps, or check for su binary: 'adb shell which su' and 'adb shell ls /system/app/Superuser.apk'
    Affected if Device has root access (enables the attack vector)
  4. Check for root detection in the app
    Inspect app for root detection code using APK analysis tools (e.g., jadx, MobSF) and look for root/Superuser detection methods
    Affected if No root detection mechanisms found in the app code

User is affected if Payeer Android app version 2.5.0 or earlier is installed on a rooted device without adequate root detection protections.

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

The fix requires implementing proper server-side validation of the current PIN before accepting changes, combined with secure client-side authentication checks. Additional hardening such as root detection, code obfuscation, and tamper detection should be considered to impede dynamic instrumentation attacks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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