dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-61119

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
Kanova Android App version 1.0.27 (package name com.karelane), developed by Karely L.L.C., contains improper access control vulnerabilities. Attackers may gain unauthorized access to user details and obtain group information, including entry codes, by manipulating API request parameters. Successful exploitation could result in privacy breaches, unauthorized group access, 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 Kanova Android app version 1.0.27 contains improper access control vulnerabilities in its API endpoints. Attackers can manipulate API request parameters to bypass authorization checks, enabling unauthorized access to user personal details and sensitive group information including entry codes. This represents a classic Insecure Direct Object Reference (IDOR) or broken access control vulnerability where server-side validation of user permissions is insufficient or missing.

MitigationImplement proper server-side authorization checks on all API endpoints to verify the requesting user has legitimate permission to access the requested resources. Additionally, avoid exposing sensitive identifiers (such as group entry codes) directly in API responses and implement indirect references.

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. Verify the installed Kanova Android app version
    Open the app's settings or the device's app info screen to view the installed version number. Alternatively, check the app's entry in the device's application manager for the version label.
    Affected if The installed version is 1.0.27 (or any version known to contain this vulnerability, based on vendor guidance)
  2. Inspect API traffic for user personal details endpoints
    Use a network proxy (such as Burp Suite, OWASP ZAP, or mitmproxy) to intercept HTTP/HTTPS traffic between the Kanova app and its server. Log in with one user account and request personal details endpoints.
    Affected if The API allows retrieving another user's personal details by manipulating request parameters (such as user ID) without proper authorization validation
  3. Inspect API traffic for group information endpoints
    With the same network proxy setup, access group-related API endpoints. Attempt to access groups you do not own or are not a member of by modifying group identifiers in the request.
    Affected if The API returns sensitive group information including entry codes for groups the requesting user does not have permission to access
  4. Test for IDOR via parameter manipulation
    Intercept API requests that include object identifiers (such as user IDs, group IDs, or record IDs). Modify these identifiers to values belonging to other users or groups and observe the API response.
    Affected if The server returns data for objects the authenticated user should not be able to access based on improper or missing server-side authorization checks
  5. Check if sensitive identifiers are exposed in API responses
    Review the raw JSON or XML responses from the API endpoints using the network proxy. Look for fields such as entry codes, private keys, or other sensitive identifiers that should not be exposed to the client.
    Affected if Sensitive identifiers such as group entry codes are visible directly in API response payloads when they should be hidden or require elevated privileges to view

You are affected if you are running Kanova Android app version 1.0.27 (or an unpatched version) and the API endpoints permit unauthorized access to user personal details or sensitive group information via parameter manipulation.

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 server-side authorization checks on all API endpoints to verify the requesting user has legitimate permission to access the requested resources. Additionally, avoid exposing sensitive identifiers (such as group entry codes) directly in API responses and implement indirect references.

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