# CVE-2025-9671: UAB Paytend App com.passport.cash AndroidManifest.xml improper export of android application components

> Local attackers can exploit improperly exported Android components in the Paytend App to bypass security controls.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-5h8r-8rxq-rw39

## What is CVE-2025-9671?

CVE-2025-9671 is a medium-severity missing authorization vulnerability in UAB Paytend App, published on 29 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in UAB Paytend App up to 2.1.9 on Android. This impacts an unknown function of the file AndroidManifest.xml of the component com.passport.cash. Executing manipulation can lead to improper export of android application components. The attack needs to be launched locally. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-926 (Improper Export of Android Application Components)

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


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

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

## Is CVE-2025-9671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9671 is a medium-severity missing authorization vulnerability in UAB Paytend App, published on 29 Aug 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-9671 exists.

Affected product: UAB Paytend 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-9671/ (Markdown: https://insights.sbomify.com/CVE-2025-9671/index.md)
```

## Sources

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

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