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:

Undergoing Analysis

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-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

Remote Code Execution on the Router

April 12, 2026

CWE-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Remote Code Execution on the Router

April 12, 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 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

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

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare