# CVE-2025-8275: bsc Peru Cocktails App bsc.devy.peru_cocktails AndroidManifest.xml improper export of android application components

> Improperly exported Android components allow local attackers to bypass intended access restrictions and interact with the application.

- **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:** 28 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-25fv-pc88-fq56

## What is CVE-2025-8275?

CVE-2025-8275 is a medium-severity missing authorization vulnerability in bsc Peru Cocktails App, published on 28 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in bsc Peru Cocktails App 1.0.0 on Android. Affected by this issue is some unknown functionality of the file AndroidManifest.xml of the component bsc.devy.peru_cocktails. The manipulation leads to improper export of android application components. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2025-8275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8275 is a medium-severity missing authorization vulnerability in bsc Peru Cocktails App, published on 28 Jul 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-8275 exists.

Affected product: bsc Peru Cocktails 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-8275/ (Markdown: https://insights.sbomify.com/CVE-2025-8275/index.md)
```

## Sources

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

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