Is this vulnerability remotely exploitable?

Yes, in environments where File Browser is exposed through a proxy authentication layer, any user who can authenticate via the proxy and trigger auto-provisioning can be affected, assuming they receive unintended execute/command permissions.

What level of access does an attacker need?

An attacker needs valid access to the upstream proxy/SSO or another identity provider integrated with File Browser. They do not need prior local File Browser credentials if the instance auto-creates accounts on first proxy-auth login.

What is the safest general fix pattern?

Ensure that all auto-provisioned users, regardless of authentication method, are created with least-privilege roles that exclude command execution by default. Permission hardening should be centralized so any user creation path enforces the same restricted baseline.

Severity:

HIGH RISK

(8.1)

Improper Privilege Management (CWE-269) in File Browser Proxy Authentication Auto-Provisioning

CVE-2026-35607

Published:

Apr 7, 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-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Improper Privilege Management

CWE:

CWE-269

Impact:

Privilege Escalation and Unauthorized Command Execution

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Privilege Management

CWE:

CWE-269

Impact:

Privilege Escalation and Unauthorized Command Execution

Severity:

HIGH RISK

(8.1)

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

Improper Privilege Management (CWE-269) in File Browser Proxy Authentication Auto-Provisioning

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.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

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