Skip to content
Fencer Vulns
high 7.5

CVE-2020-8295 json

A wrong check in Nextcloud Server 19 and prior allowed to perform a denial of service attack when resetting the password for a user.

published 2021-01-26 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-29163

cvss
7.5
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

A wrong check in Nextcloud Server 19 and prior allowed to perform a denial of service attack when resetting the password for a user.

Patch / fix

  • nextcloud nextcloud_server 20.0.0
  • nextcloud Package Hub 15 SP3, Package Hub 15 SP2, Package Hub 15 SP1 +3 more 20.0.11-bp153.2.3.1
  • nextcloud Package Hub 15 SP2 20.0.7-bp152.2.6.1
  • nextcloud openSUSE Leap 15.2 20.0.7-lp152.3.6.1

opensuse advisories openSUSE-SU-2021:1068-1openSUSE-SU-2021:0274-1openSUSE-SU-2021:0262-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-8295 updated cvss 7.5

nextcloud: Denial of service attack when resetting the password for a user

  • 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.83% 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/812754 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • n/a Nextcloud Server

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.