Unauthorized revision disclosure via mismatched page identifiers
Published Sep 1, 2026 · Updated Sep 2, 2026
Authorization bypass in GROWI 8.0.2 and earlier allows remote authenticated users to read revisions from pages they cannot access. GET /_api/v3/revisions/:id checks permission for the pageId query value but fetches the revision named by the independent path value without verifying its owning page. Any authenticated account with access to one page can pair that page identifier with another page's revision identifier, exposing revision content but not modifying it.
Summary
What happened
Authorization bypass in GROWI 8.0.2 and earlier allows remote authenticated users to read revisions from pages they cannot access. GET /_api/v3/revisions/:id checks permission for the pageId query value but fetches the revision named by the independent path value without verifying its owning page. Any authenticated account with access to one page can pair that page identifier with another page's revision identifier, exposing revision content but not modifying it.
The record
- CVE
- CVE-2026-84205
- Published
- Sep 1, 2026
- Updated
- Sep 2, 2026
- Vendor
- WESEEK, Inc.
- Product
- GROWI
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=8.0.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo