CVE-2026-53620: GROWI authorization bypass in bookmark folder APIs

CVE-2026-53620 · Severity: medium · CVSS 6.3 · Published 2026-08-31

GROWI is a popular open-source wiki and knowledge management platform. This vulnerability allows an authenticated attacker to retrieve, modify, or delete other users' bookmarks through improper authorization checks in the API, potentially exposing or corrupting sensitive user data stored within the platform.

Quick answers

Is CVE-2026-53620 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53620 being exploited in the wild.
How severe is CVE-2026-53620?
Medium severity, with a CVSS score of 6.3, published 31 August 2026.
Which products and versions are affected?
GROWI GROWI v8.0.0 and earlier.
Is there a fix for CVE-2026-53620?
A patch was published on 2026-08-28: GROWI v8.0.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53620 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-53620?
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 authorization bypass (CWE-639) in GROWI's bookmark folder APIs where user-controlled keys are used without proper validation. An authenticated attacker can manipulate API requests to access, modify, or delete bookmark data belonging to other users. The vulnerability requires authentication to exploit but does not require user interaction. The attack is network-accessible. A patch is available in GROWI v8.0.1 and later.

Affected products

  • GROWI GROWI v8.0.0 and earlier

Timeline

  • 2026-08-31: disclosed
  • 2026-08-28: patched: GROWI v8.0.1 released

References

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