CVE-2018-16464 json
A missing access check in Nextcloud Server prior to 14.0.0 could lead to continued access to password protected link shares when the owner…
published 8y ago modified 4mo ago also EUVD-2018-8300
- cvss
- 5.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
A missing access check in Nextcloud Server prior to 14.0.0 could lead to continued access to password protected link shares when the owner had changed the password.
Patch / fix
- nextcloud nextcloud_server 14.0.0
Is CVE-2018-16464 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-16464 updated cvss 3.7
nextcloud: Improper authentication on public shares
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.7 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
Affected products
- n/a Nextcloud Server
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
nextcloud.com
/security/advisory/?id=NC-SA-2018-012
vendor-advisory
-
hackerone.com
/reports/146133
third-party-advisory
Sources
- CVE List CVE-2018-16464
- NVD CVE-2018-16464
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.