dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-61118

HIGH · 7.5 CVSS v3.1 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
mCarFix Motorists App version 2.3 (package name com.skytop.mcarfix), developed by Paniel Mwaura, contains improper access control vulnerabilities. Attackers may bypass verification to arbitrarily register accounts, and by tampering with sequential numeric IDs, gain unauthorized access to user data and groups. Successful exploitation could result in fake account creation, privacy breaches, and misuse of the platform.

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 mCarFix Motorists App v2.3 contains improper access control allowing attackers to bypass verification during account registration and exploit insecure direct object references (IDOR) by manipulating sequential numeric user IDs to access unauthorized user data and groups.

MitigationImplement proper authentication with verification requirements for account registration and add explicit authorization checks for all data access endpoints, replacing sequential IDs with non-predictable identifiers.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 mCarFix Motorists App installation
    Locate the mCarFix Motorists App in the environment and confirm version 2.3. Check application inventory, installed packages on mobile devices, or system software listings for the exact version string.
    Affected if The mCarFix Motorists App version 2.3 is present in the environment
  2. Test account registration verification bypass
    Create a new account via the registration flow and attempt to access protected features or data without completing any verification steps (email confirmation, phone OTP, etc.). Observe whether the account is granted active status without verification.
    Affected if Account registration completes and provides access without requiring verification completion
  3. Inspect user ID format for sequential patterns
    Examine API responses, user profile data, or application database records to determine if user identifiers use sequential numeric values (1, 2, 3, etc.) rather than random UUIDs or non-predictable identifiers.
    Affected if User IDs are sequential numeric integers rather than non-predictable values
  4. Test IDOR via user ID parameter manipulation
    Make authenticated API requests or application actions while modifying the user ID parameter (in URLs, JSON payloads, or form data) to values corresponding to other users. Verify if unauthorized data is returned or modifications succeed.
    Affected if Accessing or modifying another user's data succeeds by changing the user ID parameter to a different sequential value
  5. Check group endpoint authorization
    Access group-related API endpoints or application features using different user IDs and observe whether unauthorized users can view, join, or modify group memberships.
    Affected if Group membership data is accessible or modifiable without proper authorization checks

The environment is affected if mCarFix Motorists App v2.3 is installed and permits account creation without verification or exposes sequential user IDs that allow unauthorized access to other users data and groups.

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 proper authentication with verification requirements for account registration and add explicit authorization checks for all data access endpoints, replacing sequential IDs with non-predictable identifiers.

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