# CVE-2025-58481: Missing authorization in MotionPhoto

> Local attackers can start a privileged service in the Samsung MotionPhoto app due to improper access control, leading to privilege escalation.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Dec 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-g6h3-wh73-8f7c

## What is CVE-2025-58481?

CVE-2025-58481 is a high-severity missing authorization vulnerability in Samsung Mobile MotionPhoto, published on 2 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper access control in MPRemoteService of MotionPhoto prior to version 4.1.51 allows local attackers to start privileged service.

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

It affects 1 product.


Products: Samsung Motionphoto.

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

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

## Is CVE-2025-58481 being exploited?

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

## Other vulnerabilities in Samsung Mobile MotionPhoto

- [CVE-2025-58482](https://insights.sbomify.com/CVE-2025-58482/): Missing authorization in MotionPhoto (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58481 is a high-severity missing authorization vulnerability in Samsung Mobile MotionPhoto, published on 2 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-58481 in the wild and no public exploit code.

Affected product: Samsung Mobile MotionPhoto. 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-58481/ (Markdown: https://insights.sbomify.com/CVE-2025-58481/index.md)
```

## Sources

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

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