# CVE-2026-56124: phpUploader < 2.0.2 Unauthenticated Database Exposure via index model

> Unauthenticated attackers can view sensitive database contents including IP addresses and key hashes by accessing any page of the phpUploader application.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-wghr-7f2j-9x3f

## What is CVE-2026-56124?

CVE-2026-56124 is a high-severity vulnerability in shimosyan phpUploader, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

phpUploader before 2.0.2 contains an unauthenticated information disclosure vulnerability that allows remote attackers to access the full contents of the uploaded-files database table by visiting any page of the application. The index model executes an unbounded SELECT query and embeds the complete JSON-encoded result set in an inline script block, exposing uploader IP addresses, Argon2ID key hashes, internal filenames, and SHA-256 fingerprints.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-56124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56124 is a high-severity vulnerability in shimosyan phpUploader, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56124 in the wild and no public exploit code.

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

## Sources

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

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