# CVE-2025-45156: Business logic in n/a

> Free-tier users can bypass server-side location update interval restrictions, potentially causing excessive data usage or server load.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-3m4m-v7p2-vg4g

## What is CVE-2025-45156?

CVE-2025-45156 is a medium-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Splashin iOS v2.0 fails to enforce server-side interval restrictions for location updates for free-tier users.

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

It affects 1 product.


Products: Splashin Splashin.

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

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

## Is CVE-2025-45156 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-45157](https://insights.sbomify.com/CVE-2025-45157/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45156 is a medium-severity vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-45156 in the wild and no public exploit code.

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

## Sources

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

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