dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-56467

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue was discovered in AXIS BANK LIMITED Axis Mobile App 9.9 that allows attackers to obtain sensitive information without a UPI PIN, such as account information, balances, transaction history, and unspecified other information. NOTE: the Supplier's perspective is that this is an intended feature and "does not reveal much sensitive information."

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 Axis Mobile App version 9.9 contains an authentication/authorization flaw that allows unauthenticated attackers to access sensitive banking information including account details, balances, and transaction history without requiring UPI PIN verification. This represents a broken access control vulnerability where sensitive endpoints are exposed without proper authentication checks.

MitigationImplement proper authentication and authorization checks for all sensitive endpoints to ensure UPI PIN or equivalent authentication is required before exposing account information, balances, and transaction history. Conduct security testing to verify unauthorized access is blocked.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Axis Mobile App version
    On Android, navigate to Settings > Apps > Axis Mobile and check the version field. On iOS, go to Settings > Axis Mobile. Note the exact version number displayed.
    Affected if The installed version is 9.9 exactly, matching the affected version in the CVE.
  2. Capture and inspect API traffic for authentication requirements
    Set up a network proxy (such as Burp Suite, OWASP ZAP, or Charles Proxy) on a test device with the Axis Mobile App installed. Initiate a session and observe the HTTP/HTTPS requests made to banking endpoints.
    Affected if API requests to sensitive endpoints (account details, balance, transactions) are sent without requiring a UPI PIN or session token in the request.
  3. Test account details endpoint access without authentication
    Using the captured API traffic as reference, attempt a direct HTTP request to the account details endpoint without including any authentication headers, cookies, or UPI PIN parameters.
    Affected if The endpoint returns full account holder details without rejecting the request for missing authentication.
  4. Test balance inquiry endpoint access without UPI PIN
    Identify the balance query API endpoint from captured traffic. Make a direct request to this endpoint excluding any UPI PIN or authentication token from the payload.
    Affected if Current account balance is returned in the response without the request being rejected due to missing UPI PIN verification.
  5. Test transaction history endpoint access without authentication
    Locate the transaction history or mini-statement endpoint from API traffic. Send a request to this endpoint without providing UPI PIN or any valid authentication credential in the request body or headers.
    Affected if Transaction history including past transfers, payments, or deposits is exposed without requiring UPI PIN verification.

The environment is affected if the Axis Mobile App version 9.9 is installed and any of the sensitive banking endpoints (account details, balances, or transaction history) return data without enforcing UPI PIN or equivalent authentication.

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 and authorization checks for all sensitive endpoints to ensure UPI PIN or equivalent authentication is required before exposing account information, balances, and transaction history. Conduct security testing to verify unauthorized access is blocked.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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