Cloudreve: Unauthorized file write via WOPI view sessions whose access token secret is ignored
cloudreve
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cloudreve/Cloudreve/v4 Go |
|
|
| github.com/cloudreve/Cloudreve/v3 Go |
| No fix yet |
cloudreve
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cloudreve/Cloudreve/v4 Go |
|
|
| github.com/cloudreve/Cloudreve/v3 Go |
| No fix yet |
|
| No fix yet |
Cloudreve is a self-hosted file management and sharing system. Prior to 4.17.0, ViewerSessionValidation uses only the session-id prefix of a WOPI access token and does not enforce the requested viewer action, allowing a malicious or compromised WOPI viewer with a view session to forge the token suffix and invoke WOPI write routes for the underlying file. This issue is fixed in version 4.17.0.
From the CVE record · GitHub_M
Cloudreve's WOPI viewer session validation checks only the session-ID prefix of an access token and does not enforce the requested action. A malicious or compromised WOPI viewer with a view session can forge the token suffix and call WOPI write routes for the underlying file.
Operators of Cloudreve before 4.17.0 should check their deployments, including Go package github.com/cloudreve/Cloudreve/v4 before 4.0.0-20260626022433-f3347130ac48; the listed v3 and unversioned Go packages have no fix.