# CVE-2026-34381: Admidio: Unauthenticated Access to Role-Restricted documents via neutralized .htaccess

> Unauthenticated attackers can access role-restricted documents in Admidio Docker deployments due to ignored .htaccess files, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-7fh7-8xqm-3g88

## What is CVE-2026-34381?

CVE-2026-34381 is a high-severity missing authorization vulnerability in admidio, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Admidio is an open-source user management solution. From version 5.0.0 to before version 5.0.8, Admidio relies on adm_my_files/.htaccess to deny direct HTTP access to uploaded documents. The Docker image ships with AllowOverride None in the Apache configuration, which causes Apache to silently ignore all .htaccess files. As a result, any file uploaded to the documents module regardless of the role-based permissions configured in the UI, is directly accessible over HTTP without authentication by anyone who knows the file path. The file path is disclosed in the upload response JSON. This issue has been patched in version 5.0.8.

Weakness: CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including admidio/admidio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | From 5.0.0 | 5.0.8 |
| `admidio/admidio` | Packagist | From 5.0.0 | 5.0.8 |

Products: Admidio Admidio.

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

Upgrade admidio/admidio to 5.0.8 or later.

## Is CVE-2026-34381 being exploited?

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

## Other vulnerabilities in admidio

- [CVE-2024-37906](https://insights.sbomify.com/CVE-2024-37906/): Admidio has Blind SQL Injection in ecard_send.php (critical 10.0)
- [CVE-2021-32630](https://insights.sbomify.com/CVE-2021-32630/): Various (critical 9.6)
- [CVE-2026-32817](https://insights.sbomify.com/CVE-2026-32817/): Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion (critical 9.1)
- [CVE-2024-38529](https://insights.sbomify.com/CVE-2024-38529/): Admidio Vulnerable to RCE via Arbitrary File Upload in Message Attachment (critical 9.1)
- [CVE-2026-32756](https://insights.sbomify.com/CVE-2026-32756/): Admidio: Unrestricted File Upload via CSRF Token Validation Bypass in Documents & Files Module (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34381 is a high-severity missing authorization vulnerability in admidio, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34381 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected from 5.0.0; fixed in 5.0.8
- admidio/admidio (Packagist): affected from 5.0.0; fixed in 5.0.8

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-34381/ (Markdown: https://insights.sbomify.com/CVE-2026-34381/index.md)
```

## Sources

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

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