# CVE-2026-85401: Dolibarr Legacy File Manager config.inc.php access control

> Remote attackers can bypass access controls in the Legacy File Manager to read or modify configuration files, requiring an upgrade to Dolibarr.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-j5c5-5r34-44pm

## What is CVE-2026-85401?

CVE-2026-85401 is a medium-severity missing authorization vulnerability in Dolibarr, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in Dolibarr up to 21.0.4/22.0.5/23.0.3. Affected by this issue is some unknown functionality of the file htdocs/core/filemanagerdol/connectors/php/config.inc.php of the component Legacy File Manager. Executing a manipulation can lead to improper access controls. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 23.0.4 can resolve this issue. This patch is called ef6631e9bd5ec4b8cec0e88f1796d3d10dad02ec. It is suggested to upgrade the affected component.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-85401?


## How do I fix CVE-2026-85401?

No fix has been published for CVE-2026-85401 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85401 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85401 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85401 and fix it if it is affected.

What it is: CVE-2026-85401 is a medium-severity missing authorization vulnerability in Dolibarr, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85401 exists.

Affected product: Dolibarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85401/ (Markdown: https://insights.sbomify.com/CVE-2026-85401/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85401
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85401
- OSV: https://osv.dev/vulnerability/CVE-2026-85401

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85401/
Summaries are generated and may contain mistakes; the official description above is the record.