Skip to content
Fencer Intel
low 2.0

CVE-2021-25525 json

Improper check or handling of exception conditions vulnerability in Samsung Pay (US only) prior to version 4.0.65 allows attacker to use NF…

published 4y ago modified 4mo ago also EUVD-2021-12421

cvss
2.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

Improper check or handling of exception conditions vulnerability in Samsung Pay (US only) prior to version 4.0.65 allows attacker to use NFC without user recognition.

Patch / fix

  • Samsung Mobile Samsung Pay 4.0.65

Is CVE-2021-25525 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.0 CVSS:3.1/AV:P/AC:L/PR:H/UI:R/S:C/C:N/I:N/A:L
NVD 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Samsung Mobile Samsung Pay

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.