Bypass lock protection in the Nextcloud Android app prior to version 3.3.0 allowed access to files when being prompted for the lock protect…

published 2019-07-30 7y ago modified 2026-06-17 4mo ago also EUVD-2019-15037

cvss: 6.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

Bypass lock protection in the Nextcloud Android app prior to version 3.3.0 allowed access to files when being prompted for the lock protection and switching to the Nextcloud file provider.

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

Exploits and checks

hackerone.com https://hackerone.com/reports/331489 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

Nextcloud com.nextcloud.client

Classification

Weakness

CWE-288 Authentication Bypass Using an Alternate Path or Channel
CWE-287 Improper Authentication

References

hackerone.com /reports/331489
exploit, third-party-advisory

Sources

CVE List CVE-2019-5453
NVD CVE-2019-5453

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.