Skip to content
Fencer Intel
medium 6.8

CVE-2013-5113 json

LastPass prior to 2.5.1 has an insecure PIN implementation.

published 6y ago modified 4mo ago also EUVD-2013-4954

cvss
6.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

LastPass prior to 2.5.1 has an insecure PIN implementation.

Patch / fix

  • logmein lastpass 2.5.1

Is CVE-2013-5113 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.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • blog.c22.cc http://blog.c22.cc/2013/09/05/a-sneak-peak-into-android-secure-containers-2/ referenced PoC, tagged "exploit" by a source, unverified
  • blog.c22.cc https://blog.c22.cc/advisories/cve-2013-51135114-lastpass-android-container-pin-and-auto-wipe-security-feature-bypass/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

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.