# CVE-2026-84715: FeatherPanel before 1.3.7.10 Privilege Escalation via Subuser Permission Update

> Authenticated subusers can escalate privileges to full server control by modifying their own permission records due to missing validation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 2 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-2cvx-7j4v-8m5g

## What is CVE-2026-84715?

CVE-2026-84715 is a high-severity vulnerability in MythicalLTD FeatherPanel, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FeatherPanel versions before 1.3.7.10 fail to validate permissions in the SubuserController updateSubuser handler, allowing authenticated subusers to modify their own permission records. A subuser with minimal permissions can send a crafted request to grant themselves full server control, enabling unauthorized access to sensitive data, backups, and server configuration.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-84715 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84715 is a high-severity vulnerability in MythicalLTD FeatherPanel, published on 2 Sep 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-84715 in the wild and no public exploit code.

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

## Sources

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

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