# CVE-2026-10806: mjperpinosa stumasy add_post.php unrestricted upload

> Remote attackers can upload arbitrary files via the add_post.php script, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-fpp3-9qqr-4xxm

## What is CVE-2026-10806?

CVE-2026-10806 is a medium-severity vulnerability in mjperpinosa stumasy, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in mjperpinosa stumasy. The affected element is an unknown function of the file application/PHP/objects/updates/add_post.php. Performing a manipulation of the argument up_file_to_post results in unrestricted upload. The attack may be initiated remotely. The exploit has been made public and could be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-10806 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10806 is a medium-severity vulnerability in mjperpinosa stumasy, published on 4 Jun 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-10806 exists.

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

## Sources

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

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