# CVE-2025-41458: Insecure data storage vulnerability in Two App Studio Journey v5.5.9 for iOS

> Local attackers can extract sensitive data from the app's unencrypted database via direct filesystem access on iOS devices.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 21 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-vx6m-h78h-xxcf

## What is CVE-2025-41458?

CVE-2025-41458 is a medium-severity vulnerability in Two App Studio Journey, published on 21 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unencrypted storage in the database in Two App Studio Journey v5.5.9 for iOS allows local attackers to extract sensitive data via direct access to the app’s filesystem.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2025-41458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41458 is a medium-severity vulnerability in Two App Studio Journey, published on 21 Jul 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-41458 in the wild and no public exploit code.

Affected product: Two App Studio Journey. 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-41458/ (Markdown: https://insights.sbomify.com/CVE-2025-41458/index.md)
```

## Sources

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

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