Is this vulnerability remotely exploitable?

Yes. If the FileRise instance is network-accessible and still uses the default key, an attacker who knows the hardcoded value can interact with the public endpoints and exploit the issue remotely without local access.

Does exploitation require authentication or valid user access?

No. The vulnerability is exploitable by unauthenticated users, because the default key is sufficient to generate valid tokens and decrypt configuration without possessing any legitimate credentials.

What is the safest general fix pattern?

The safest approach is to remove reliance on any hardcoded default key and require a strong, deployment-specific secret to be configured explicitly for each environment. Additionally, use separate keys for different cryptographic purposes and ensure the application refuses to start if these secrets are missing or invalid.

Severity:

HIGH RISK

(8.2)

Hardcoded Cryptographic Key (CWE-798) in FileRise Web File Manager

CVE-2026-33072

Published:

Mar 20, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Hardcoded Cryptographic Key / Insecure Key Management

CWE:

CWE-798;CWE-1188

Impact:

Authentication and Authorization Bypass, Confidentiality Breach, and Integrity Compromise

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Hardcoded Cryptographic Key / Insecure Key Management

CWE:

CWE-798;CWE-1188

Impact:

Authentication and Authorization Bypass, Confidentiality Breach, and Integrity Compromise

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Hardcoded Cryptographic Key (CWE-798) in FileRise Web File Manager

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal