CVE-2025-56467: An issue was discovered in AXIS BANK LIMITED Axis Mobile App 9.9 that allows attackers to obtain sensitive...
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."
Security readout for executives and security teams
Plain-English summary
CVE-2025-56467 describes possible exposure of Axis Bank mobile banking information without requiring a UPI PIN. Reported data includes account information, balances, transaction history, and other unspecified information. The supplier reportedly considers this intended behavior and disputes the sensitivity, so business impact depends on what data is actually exposed in deployed app flows.
Executive priority
Handle as a moderate confidentiality issue. It does not show confirmed active exploitation, integrity loss, or availability impact, but financial account visibility can create privacy, fraud, and customer-trust risk if the behavior is present at scale.
Technical view
The CVE maps to CWE-200 with CVSS 3.1 score 6.5. The vector indicates network access, low complexity, low privileges, no user interaction, and high confidentiality impact only. The source bundle names Axis Mobile App 9.9, but the affected product metadata is incomplete and lists vendor/product/version as n/a.
Likely exposure
Likely exposure is limited to users or organizations relying on Axis Mobile App 9.9, based on the CVE description. The official affected-product fields are incomplete, so confirm against Axis Bank guidance before drawing scope conclusions.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. A public researcher write-up is referenced, and one duplicate CVE reference is tagged exploit, but that does not establish real-world exploitation.
Researcher notes
Evidence is thin and partially disputed. The supplier’s stated position conflicts with the CVE’s confidentiality framing. Prioritize verification of actual data exposure, authentication state, affected versions, and whether the duplicated malformed reference reflects source-quality issues.
Mitigation direction
Check Axis Bank advisories and app-store release notes for official remediation guidance.
Update the Axis Mobile App through official stores when a relevant update is available.
Avoid sharing devices or app sessions where banking data may be visible.
Treat exposed balances and transaction history as sensitive personal financial data.
Escalate privacy and fraud-monitoring review if confirmed in your user population.
Validation and detection
Confirm whether affected users have Axis Mobile App 9.9 installed.
Review official CVE fields and Axis Bank statements for corrected affected-version data.
Using an authorized test account, identify what data appears before UPI PIN entry.
Document whether balances, account details, or transaction history are exposed.
Check whether newer app versions change the pre-UPI-PIN data exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.