Unauthorized file writes via unenforced WOPI tokens
Published Jul 31, 2026 · Updated Jul 31, 2026
Incorrect authorization in Cloudreve before 4.17.0 allows remote attackers controlling a WOPI viewer to write user files via view sessions. ViewerSessionValidation loads a session by the access token's ID prefix without comparing its random suffix, while WOPI write routes ignore the requested viewer action. Exploitation requires a configured WOPI viewer and a view URL or session ID; writes remain limited to files that the session user can modify.
Summary
What happened
Incorrect authorization in Cloudreve before 4.17.0 allows remote attackers controlling a WOPI viewer to write user files via view sessions. ViewerSessionValidation loads a session by the access token's ID prefix without comparing its random suffix, while WOPI write routes ignore the requested viewer action. Exploitation requires a configured WOPI viewer and a view URL or session ID; writes remain limited to files that the session user can modify.
The record
- CVE
- CVE-2026-62323
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Cloudreve
- Product
- Cloudreve
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 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=< 4.17.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- GitHub advisory WOPI forged-token reproductionproof of concept · demonstrated
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