CVE-2026-84204: GROWI access control bypass in attachment API

CVE-2026-84204 · Severity: medium · CVSS 6.5 · Published 2026-09-01

GROWI is a team collaboration and wiki platform. An access control vulnerability in its attachment API allows authenticated users to retrieve metadata about files attached to pages they do not have permission to view. An attacker could use this to discover sensitive documents or attachment information that should be restricted.

Quick answers

Is CVE-2026-84204 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-84204 being exploited in the wild.
How severe is CVE-2026-84204?
Medium severity, with a CVSS score of 6.5, published 1 September 2026.
Which products and versions are affected?
GROWI Labs GROWI before v8.0.3 (v8.0.2 confirmed vulnerable).
Is there a fix for CVE-2026-84204?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-84204 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-84204?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an access control bypass (CWE-639) in the GET /_api/v3/attachment/:id endpoint. The endpoint fails to validate whether the authenticated user has permission to access the page associated with a requested attachment. An attacker with valid credentials can enumerate or retrieve attachment metadata by supplying known attachment identifiers, even for pages marked as private or restricted. The vulnerability requires authentication but no special privileges. A fix is available in versions after v8.0.2.

Affected products

  • GROWI Labs GROWI before v8.0.3 (v8.0.2 confirmed vulnerable)

Timeline

  • 2026-09-01: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.