# CVE-2026-113472: Depicter 4.0.5 - 4.8.1 - Editor+ Arbitrary File Upload via Media Upload


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-f92x-x728-fq7r

## What is CVE-2026-113472?

CVE-2026-113472 is a medium-severity vulnerability in Unknown Depicter — Popup & Slider Builder, published on 23 Oct 2026. 

### Official description

The Depicter — Popup & Slider Builder WordPress plugin before 4.8.2 does not properly validate uploaded files in its editor media-upload endpoint, checking only the client-supplied MIME type and a case-sensitive block of the .php extension, which allows users with the Editor role and above to upload files with other active extensions into the public uploads directory, leading to stored script execution in the site origin and, depending on the server's handler mapping, to code execution.

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

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


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

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

## Is CVE-2026-113472 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113472 is a medium-severity vulnerability in Unknown Depicter — Popup & Slider Builder, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113472 in the wild and no public exploit code.

Affected product: Unknown Depicter — Popup & Slider Builder. 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-113472/ (Markdown: https://insights.sbomify.com/CVE-2026-113472/index.md)
```

## Sources

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

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