dbcve.org
MotionphotoApplication · Samsung

CVE-2025-58482

HIGH · 7.3 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 4.1.51 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper access control in MPLocalService of MotionPhoto prior to version 4.1.51 allows local attackers to start privileged service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper access control in MPLocalService of the MotionPhoto application prior to version 4.1.51 allows local attackers to start a privileged service. This is a local privilege escalation vulnerability where the service lacks proper authorization checks before allowing service initiation.

MitigationUpdate MotionPhoto to version 4.1.51 or later. If patching is not possible, restrict local access to the device and ensure no untrusted applications can interact with MPLocalService.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MotionphotoApplication
Affected:< 4.1.51

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MotionPhoto app is installed
    Open Android Settings > Apps > MotionPhoto, or use ADB command: pm list packages | grep motionphoto
    Affected if MotionPhoto package is found on the device
  2. Determine installed MotionPhoto version
    Navigate to MotionPhoto app info in Settings > Apps > MotionPhoto > App info, or use ADB: dumpsys package com.samsung.android.motionphoto | grep versionName
    Affected if Version shown is less than 4.1.51 or version cannot be determined (unlisted)
  3. Verify MPLocalService component exists
    Use ADB to check if the service is exposed: dumpsys package com.samsung.android.motionphoto | grep -i mplocalservice
    Affected if MPLocalService component is registered and visible in package dump
  4. Check if service accepts external intents
    Review app manifest via ADB: pm dump com.samsung.android.motionphoto | grep -A20 MPLocalService, or use an app analysis tool to inspect exported service components
    Affected if Service is exported and does not require signature-level permissions for invocation

If MotionPhoto version is below 4.1.51 and MPLocalService is exposed without proper authorization, the device is vulnerable to local privilege escalation via untrusted app invocation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.51 or later
Fixed in 4.1.51
Interim mitigation

Update MotionPhoto to version 4.1.51 or later. If patching is not possible, restrict local access to the device and ensure no untrusted applications can interact with MPLocalService.

Recommended fix High confidence

4.1.51

  1. Ensure your Samsung device is connected to Wi-Fi or cellular network
  2. Open the Samsung Galaxy Store or Google Play Store
  3. Search for "MotionPhoto" or "Motion photo" in the app store
  4. Locate the MotionPhoto application and verify the current version
  5. If the installed version is below 4.1.51, tap Update to install version 4.1.51 or later
  6. Alternatively, check for system software updates via Settings > Software Update > Download and install
  7. After updating, verify the version number matches 4.1.51 or higher to confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Motionphoto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58482 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data