Skip to main content

Filerise EUVDEUVD-2026-13643

| CVE-2026-33072 HIGH
Use of Hard-coded Credentials (CWE-798)
2026-03-20 GitHub_M
8.2
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify hardcoded encryption key in FileRise
  2. Delivery
    Forge upload tokens using default key
  3. Exploit
    Upload arbitrary files to shared folders
  4. Execution
    Decrypt admin configuration with same key
  5. Impact
    Extract OIDC and SMTP credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

FileRise versions prior to 3.9.0 with default encryption key unchanged (default_please_change_this_key). Remote unauthenticated attacker can forge upload tokens and decrypt admin secrets without victim interaction.

Impact

The CVSS score of 8.2 (High) reflects network-based exploitation with low complexity requiring no authentication or user interaction, with high confidentiality impact and low integrity impact. The attack vector (AV:N) and lack of required privileges (PR:N) make this trivially exploitable by remote attackers. The vulnerability permits both arbitrary file upload (integrity impact) and decryption of sensitive administrative secrets like OIDC client secrets and SMTP passwords (confidentiality impact). While not currently listed in CISA KEV or showing elevated EPSS scores, the straightforward exploitation path and hardcoded nature of the vulnerability make it highly automatable for mass exploitation campaigns. Real-world risk is significant for any FileRise deployment that retained the default configuration, as attackers can enumerate FileRise instances and immediately exploit them without any reconnaissance or sophisticated techniques. This represents a genuine high-priority risk especially for internet-facing deployments.

Exploit ScenarioDerived

An unauthenticated remote attacker identifies a FileRise installation and uses the publicly known hardcoded key 'default_please_change_this_key' to forge valid HMAC upload tokens, enabling arbitrary file upload to shared folders without authorization. The attacker then uses the same key to decrypt AES-encrypted configuration data, extracting OIDC client secrets to pivot into connected identity providers or SMTP passwords to send phishing emails appearing to originate from the organization. Given the network-accessible attack vector and low complexity (no authentication required), exploitation can be fully automated across internet-facing FileRise instances.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

FileRise, a self-hosted web file manager and WebDAV server, contains a critical hardcoded encryption key vulnerability in versions prior to 3.9.0. The default key 'default_please_change_this_key' is used for all cryptographic operations including HMAC token generation, AES configuration encryption, and session tokens, allowing unauthenticated attackers to forge upload tokens for arbitrary file upload and decrypt sensitive admin configuration data such as OIDC client secrets and SMTP passwords. No evidence of active exploitation (not in CISA KEV) is currently available, though the vulnerability is straightforward to exploit given the hardcoded nature of the default key.

RemediationAI

Immediately upgrade FileRise to version 3.9.0 or later, which addresses the hardcoded key vulnerability according to the release notes at https://github.com/error311/FileRise/releases/tag/v3.9.0. Review the GitHub security advisory at https://github.com/error311/FileRise/security/advisories/GHSA-f4xx-57cv-mg3x for complete remediation guidance. If immediate patching is not possible, manually set the PERSISTENT_TOKENS_KEY environment variable to a cryptographically random value of sufficient length, rotate all existing session tokens, and regenerate any OIDC client secrets or SMTP passwords that may have been encrypted with the default key. Additionally, audit logs for any unauthorized file uploads or suspicious authentication activity that may indicate prior exploitation, and consider restricting network access to FileRise instances to trusted IP ranges until patching is complete.

Affected VersionsENISA

FileRise < 3.9.0

Affected Packages

euvd filerise fix: 3.9.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FileRise (CPE: cpe:2.3:a:error311:filerise:*:*:*:*:*:*:*:*) is a self-hosted web file manager with WebDAV server capabilities. This vulnerability represents CWE-798 (Use of Hard-coded Credentials), where a single cryptographic key (PERSISTENT_TOKENS_KEY) with the hardcoded default value 'default_please_change_this_key' is used across all security-sensitive operations. The key is embedded in the codebase in multiple locations and is only changed if deployers explicitly override the environment variable. This design flaw affects three critical security functions: HMAC-based upload token generation for shared folders, AES encryption of administrative configuration data, and session token generation for authentication. The vulnerability allows complete cryptographic compromise of any FileRise installation that has not manually changed the default key.

Know when Filerise gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

Lifecycle Timeline

3
Analysis Updated
Apr 16, 2026 - 06:19 EUVD-patch-fix
executive summary
Patch available
Apr 16, 2026 - 05:29 EUVD
3.9.0
CVE Published
Mar 20, 2026 - 08:31 nvd
HIGH 8.2

DescriptionGitHub Advisory

FileRise is a self-hosted web file manager / WebDAV server. In versions prior to 3.9.0, a hardcoded default encryption key (default_please_change_this_key) is used for all cryptographic operations - HMAC token generation, AES config encryption, and session tokens - allowing any unauthenticated attacker to forge upload tokens for arbitrary file upload to shared folders, and to decrypt admin configuration secrets including OIDC client secrets and SMTP passwords. FileRise uses a single key (PERSISTENT_TOKENS_KEY) for all crypto operations. The default value default_please_change_this_key is hardcoded in two places and used unless the deployer explicitly overrides the environment variable. This issue is fixed in version 3.9.0.

Executive ViewAI

Why It Matters

FileRise versions prior to 3.9.0 contain a hardcoded encryption key that enables unauthenticated attackers to forge file upload tokens and decrypt sensitive administrative credentials including OIDC secrets and SMTP passwords, potentially compromising authentication systems and email infrastructure. Organizations using self-hosted FileRise deployments face immediate risk of unauthorized file uploads and credential exposure without patching to version 3.9.0 or later.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible, restrict network access to FileRise instances to trusted internal networks only, disable WebDAV protocol if not required for business operations, and immediately rotate all credentials (OIDC client secrets, SMTP passwords) managed by the application.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Related Vulnerabilities in FileRise Authentication and Upload Issues

View all 3
CVE-2026-25231 HIGH POC
7.5 Feb 09

Unauthenticated directory traversal in FileRise prior to version 3.3.0 allows remote attackers to read arbitrary files f

CVE-2026-54414 CRITICAL
9.3 Jun 19

Unauthenticated administrator account takeover in FileRise before 3.16.0 is possible via a path traversal flaw in the sh

CVE-2025-66403 MEDIUM POC
5.4 Dec 01

Stored cross-site scripting in FileRise versions before 2.2.3 allows an authenticated user with upload rights to embed J

CVE-2026-25230 MEDIUM POC
4.6 Feb 09

FileRise versions before 3.3.0 contain an HTML injection vulnerability that allows authenticated users to manipulate the

CVE-2026-61843 HIGH
8.2 Oct 14

File overwrite in FileRise prior to 3.18.0 allows an unauthenticated visitor who holds a valid upload-enabled shared-fol

CVE-2026-57489 HIGH
8.1 Oct 14

Authentication bypass in FileRise (CWE-290) lets unauthenticated remote attackers impersonate any account - including an

CVE-2026-103977 HIGH
8.1 Oct 14

Online second-factor guessing against FileRise releases prior to 3.23.0 is permitted well beyond the intended limit beca

CVE-2026-57490 HIGH
8.1 Oct 14

Multi-factor authentication bypass in FileRise WebDAV prior to 3.16.0 allows an attacker who already holds a valid usern

CVE-2026-104108 HIGH
8.1 Oct 14

Authentication bypass in FileRise versions before 3.23.0 lets a remote attacker log in as an existing local account - in

CVE-2026-33329 HIGH
8.1 Mar 24

FileRise, a self-hosted web file manager and WebDAV server, contains a path traversal vulnerability in its Resumable.js

CVE-2025-62510 HIGH
8.1 Oct 20

FileRise 1.4.0 exposes folder visibility and ownership decisions to authenticated low-privilege users because a regressi

CVE-2025-62509 HIGH
8.1 Oct 20

Low-privilege users of FileRise versions prior to 1.4.0 can view, delete, or modify files owned by other users because t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy