# CVE-2026-103988: FileRise renameFolder omits destination-parent authorization

> Authenticated users can move folders into unauthorized locations due to missing destination parent authorization in FileRise.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-hhc9-q8vh-95p8

## What is CVE-2026-103988?

CVE-2026-103988 is a medium-severity missing authorization vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise /api/folder/renameFolder.php authorizes an authenticated, non-folder-scoped, non-administrator with a valid CSRF token against the source folder but does not independently authorize a changed destination parent. A qualifying user who owns a source folder can move that tree beneath another user's existing folder or into the root namespace, and the operation rekeys the moved ownership and ACL records to the new path. The destination must be unused and existing victim files cannot be overwritten. Distinct pre-fix errors reveal whether a specifically guessed destination path exists, but disclose no directory listing or file contents. This issue is fixed in version 3.23.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-103988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103988 is a medium-severity missing authorization vulnerability in error311 FileRise, published on 14 Oct 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-103988 exists.

Affected product: error311 FileRise. 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-103988/ (Markdown: https://insights.sbomify.com/CVE-2026-103988/index.md)
```

## Sources

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

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