Unauthenticated upload and secret decryption via hardcoded key
Published Mar 20, 2026 · Updated Mar 20, 2026
Hardcoded key use in error311 FileRise before 3.9.0 allows remote attackers to forge upload tokens and decrypt configuration secrets. The Dockerfile and config/config.php supply one published PERSISTENT_TOKENS_KEY to HMAC, AES-CBC, and session-token operations when no override exists. A shared-folder URL enables unauthenticated file upload when uploads are enabled; secret decryption additionally requires read access to adminConfig.json.
Summary
What happened
Hardcoded key use in error311 FileRise before 3.9.0 allows remote attackers to forge upload tokens and decrypt configuration secrets. The Dockerfile and config/config.php supply one published PERSISTENT_TOKENS_KEY to HMAC, AES-CBC, and session-token operations when no override exists. A shared-folder URL enables unauthenticated file upload when uploads are enabled; secret decryption additionally requires read access to adminConfig.json.
The record
- CVE
- CVE-2026-33072
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- error311
- Product
- FileRise
- Classifications
- CWE-1188, CWE-798, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=< 3.9.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.
Weakness, pattern, technique
Public exploit references
- Shared-folder upload-token forgery proof of conceptfunctional · demonstrated
- Admin configuration decryption proof of conceptfunctional · 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