# CVE-2026-47230: Admidio: IDOR in documents-files.php allows cross-folder file rename and description changes by unauthorized uploaders

> Unauthorized users can rename files and modify descriptions in folders they do not have upload rights for, due to insufficient authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-q6w3-hpfv-rg36

## What is CVE-2026-47230?

CVE-2026-47230 is a medium-severity missing authorization vulnerability in admidio, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Admidio is an open-source user management solution. Prior to version 5.0.10, `modules/documents-files.php` mode `file_rename_save` shares the same root-cause shape as the cross-folder move bug (`05-documents-cross-folder-move-idor.md`): the top-level rights check at lines 79-89 validates `hasUploadRight()` on the URL parameter `folder_uuid`, but the rename operation acts on `file_uuid` — a separate URL parameter — without re-checking the folder that actually contains the file. `DocumentsService::renameFile()` resolves the target file via `getFileForDownload()` (which permits view-readable files) but does not require upload right on the file's source folder. Result: a user with upload right on any folder A can rename a file in folder B as long as they can view it. They can also overwrite the file's description. Version 5.0.10 contains a fix.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

2 open source packages ship an affected version, including admidio/admidio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |

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

Upgrade admidio/admidio to 5.0.10 or later.

## Is CVE-2026-47230 being exploited?

There is no known exploitation of CVE-2026-47230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47230 is a medium-severity missing authorization vulnerability in admidio, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47230 in the wild and no public exploit code.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10

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

## Sources

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

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