Skip to content
Fencer Vulns
high 7.7

CVE-2020-8154 json

An Insecure direct object reference vulnerability in Nextcloud Server 18.0.2 allowed an attacker to remote wipe devices of other users when…

published 2020-05-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-29047

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

Summary

An Insecure direct object reference vulnerability in Nextcloud Server 18.0.2 allowed an attacker to remote wipe devices of other users when sending a malicious request directly to the endpoint.

Patch / fix

  • nextcloud nextcloud_server 17.0.5, 18.0.3
  • nextcloud Package Hub 15 SP2, Package Hub 15 SP1, Package Hub 12 +2 more 20.0.0-bp152.2.3.1
  • nextcloud openSUSE Leap 15.1 18.0.4-lp151.2.6.1
  • nextcloud Package Hub 15 SP1 18.0.4-bp151.3.9.1
  • nextcloud Package Hub 12 18.0.4-22.1

opensuse advisories openSUSE-SU-2020:1652-1openSUSE-SU-2020:0670-1openSUSE-SU-2020:0668-1openSUSE-SU-2020:0667-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-8154 updated

nextcloud: multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    not 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

1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

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

CVSS scores

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

Affected products

  • n/a Nextcloud Server

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Vulns 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.