dbcve.org
MembersApplication · Samsung

CVE-2025-21079

HIGH · 8.1 CVSS v3.1 Published 2025-11-05
Fix available
A fix is available. Upgrade to 5.5.01.3 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 input validation in Samsung Members prior to version 5.5.01.3 allows remote attackers to connect arbitrary URL and launch arbitrary activity with Samsung Members privilege. User interaction is required for triggering this vulnerability.

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

This is an improper input validation vulnerability in the Samsung Members Android application. The vulnerability allows an attacker to supply an arbitrary URL that the app will connect to, and subsequently launch arbitrary activities within the Samsung Members app context. Since the app runs with Samsung Members privileges, this could enable attackers to perform actions within the app's security context. The attack requires user interaction to trigger.

MitigationUpdate Samsung Members to version 5.5.01.3 or later. For organizations that cannot update, consider restricting the application's network access or removing the application if unnecessary.

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
MembersApplication
Affected:< 5.5.01.3

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Confirm Samsung Members app is installed
    Run 'adb shell pm list packages | grep samsung.members' or check in Settings > Apps for Samsung Members
    Affected if The package com.samsung.android.verticalapppatch.members or similar Samsung Members package is present on the device
  2. Retrieve installed version of Samsung Members
    Run 'adb shell dumpsys package com.samsung.android.verticalapppatch.members | grep versionName' or view app version in Play Store/App Info under 'Version'
    Affected if Unable to retrieve version information indicates the app may not be properly installed
  3. Compare installed version against vulnerable range
    Compare the retrieved version number to the affected version < 5.5.01.3. Note that version format may appear as 5.5.0.x or similar
    Affected if Installed version is numerically less than 5.5.01.3 (for example, 5.5.00.1, 5.4.x.x, etc.)
  4. Verify app is not updated via Play Store mechanism
    Check if an update is available in Galaxy Store or Google Play Store under 'App updates' or check if device auto-updates are enabled
    Affected if No update is available and version remains below 5.5.01.3

If Samsung Members is installed and its version is lower than 5.5.01.3, the device is vulnerable to CVE-2025-21079 and could be exploited if a user interacts with a malicious crafted link.

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 5.5.01.3 or later
Fixed in 5.5.01.3
Interim mitigation

Update Samsung Members to version 5.5.01.3 or later. For organizations that cannot update, consider restricting the application's network access or removing the application if unnecessary.

Recommended fix High confidence

Samsung Members version 5.5.01.3

  1. Open the Samsung Members app on your device
  2. Navigate to the app settings or menu option to check for updates
  3. Update Samsung Members to version 5.5.01.3 through the Samsung Galaxy Store
  4. Alternatively, check for system updates through Settings > Apps > Samsung Members to ensure you have the latest version

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

Fix this in Members Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21079 — 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-21079 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