# CVE-2026-56702: Adminer before 5.4.3 Unrestricted File Upload via AdminerFileUpload

> Authenticated attackers can upload PHP webshells via the AdminerFileUpload plugin to execute arbitrary code on the server.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-56702, GHSA-p84v-vg3f-p9m6, GHSA-vcvj-rwwm-x6g5, UBUNTU-CVE-2026-56702

## What is CVE-2026-56702?

CVE-2026-56702 is a high-severity vulnerability in vrana adminer, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Adminer versions before 5.4.3 contain an unrestricted file upload vulnerability in the AdminerFileUpload plugin that allows authenticated users to upload PHP files by exploiting a permissive default extension allowlist. Attackers can upload PHP webshells to columns ending in _path and execute arbitrary code as the web-server user when uploadPath is web-served.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

Upgrade to a fixed version.

## Is CVE-2026-56702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56702 is a high-severity vulnerability in vrana adminer, published on 25 Aug 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-56702 exists.

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

## Sources

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

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