# CVE-2026-57493: FileRise: Remember-me auto-login uses stale admin role from token instead of current role

> An attacker with a stale admin token retains administrator access after demotion, allowing unauthorized privilege escalation in FileRise.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-r55g-3hcc-6jx7

## What is CVE-2026-57493?

CVE-2026-57493 is a medium-severity 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.16.0, FileRise stores the isAdmin flag in remember-me tokens and restores that stale value during automatic login instead of resolving the account's current role from users.txt. A user who was issued a token while an administrator can retain administrator access after demotion, and token rotation copies the stale privilege into each replacement token. Exploitation requires possession of the pre-demotion remember-me token. This issue is fixed in version 3.16.0.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-57493 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57493 is a medium-severity 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-57493 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-57493/ (Markdown: https://insights.sbomify.com/CVE-2026-57493/index.md)
```

## Sources

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

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