# CVE-2025-20615: Qardio Heart Health IOS Mobile Application Exposure of Private Personal Information to an Unauthorized Actor

> Attackers can extract credentials from plist files to access engineering backdoors and send commands in the Qardio Heart Health iOS application.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-rjrq-626c-q262

## What is CVE-2025-20615?

CVE-2025-20615 is a medium-severity vulnerability in Qardio Heart Health IOS Mobile Application, published on 13 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Qardio Arm iOS application exposes sensitive data such as usernames 
and passwords in a plist file. This allows an attacker to log in to 
production-level development accounts and access an engineering backdoor
 in the application. The engineering backdoor allows the attacker to 
send hex-based commands over a UI-based terminal.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Qardio Qardio.

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

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

## Is CVE-2025-20615 being exploited?

There is no known exploitation of CVE-2025-20615 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-20615 is a medium-severity vulnerability in Qardio Heart Health IOS Mobile Application, published on 13 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20615 in the wild and no public exploit code.

Affected product: Qardio Heart Health IOS Mobile Application. 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-20615/ (Markdown: https://insights.sbomify.com/CVE-2025-20615/index.md)
```

## Sources

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

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