# CVE-2025-5154: PhonePe App SQLite Database databases cleartext storage in file

> Local attackers with root access can read cleartext SQLite databases, though the vendor disputes validity due to root requirements.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2025
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-q47v-w7jj-mhcf

## What is CVE-2025-5154?

CVE-2025-5154 is a medium-severity vulnerability in PhonePe App, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in PhonePe App 25.03.21.0 on Android. This affects an unknown function of the file /data/data/com.phonepe.app/databases/ of the component SQLite Database. The manipulation leads to cleartext storage in a file or on disk. The attack needs to be performed locally. The exploit is publicly available and might be used. The actual existence of this vulnerability is currently in question. The root-requirement of the attack is reflected by the CVSS vector attribute PR:H. The vendor explains: "[A]s per the PoC this vulnerability needs a rooted device to exploit. PhonePe does not consider vulnerabilities found in rooted device as valid because there is not real-world exploit scenario."

Weakness: CWE-313 (Cleartext Storage in a File or on Disk), CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-5154?

It affects 1 product.


Products: Phonepe Phonepe.

## How do I fix CVE-2025-5154?

No fix has been published for CVE-2025-5154 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5154 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5154 exists.

Public exploit code:

- https://github.com/honestcorrupt/phonepe-sensitive-data-exposure-cve-2025-5154 (github_poc): https://github.com/honestcorrupt/phonepe-sensitive-data-exposure-cve-2025-5154

## Other vulnerabilities in PhonePe App

- [CVE-2018-17401](https://insights.sbomify.com/CVE-2018-17401/): Auth bypass in n/a (high 8.8)
- [CVE-2018-17403](https://insights.sbomify.com/CVE-2018-17403/): Business logic in n/a (high 8.8)
- [CVE-2018-17400](https://insights.sbomify.com/CVE-2018-17400/): Information disclosure in n/a (high 7.0)
- [CVE-2022-45835](https://insights.sbomify.com/CVE-2022-45835/): WordPress PhonePe Payment Solutions Plugin <= 1.0.15 is vulnerable to Server Side Request Forgery (SSRF) (medium 5.8)
- [CVE-2018-17402](https://insights.sbomify.com/CVE-2018-17402/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5154 and fix it if it is affected.

What it is: CVE-2025-5154 is a medium-severity vulnerability in PhonePe App, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5154 exists.

Affected product: PhonePe App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5154/ (Markdown: https://insights.sbomify.com/CVE-2025-5154/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5154
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5154
- OSV: https://osv.dev/vulnerability/CVE-2025-5154

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5154/
Summaries are generated and may contain mistakes; the official description above is the record.