Quick answers
- Is CVE-2026-84205 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84205 being exploited in the wild.
- How severe is CVE-2026-84205?
- Medium severity, with a CVSS score of 6.5, published 1 September 2026.
- Which products and versions are affected?
- GROWI Labs GROWI.
- Is there a fix for CVE-2026-84205?
- 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-84205 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84205?
- 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 exists in the GET /_api/v3/revisions/:id endpoint, which performs access control validation against a query parameter (identifying a page) but then returns the revision data identified by the path parameter without verifying that both parameters reference the same page. An authenticated attacker can pair a page identifier they have permission to access with an arbitrary revision identifier from another restricted page to retrieve revision content from pages they lack authorization to view. This is a classic access control bypass where authorization is checked on one identifier but the actual resource fetch uses a different, unchecked identifier. The fix requires validating that both the query parameter page and the path parameter revision belong to the same page before returning revision content.
Affected products
- GROWI Labs GROWI
Timeline
- 2026-09-01: disclosed