# CVE-2026-112219: Download Monitor < 5.3.5 - Multisite Subsite Admin+ Incorrect Authorization via Approved Download Paths REST Route


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-qx3q-4jp5-2qg8

## What is CVE-2026-112219?

CVE-2026-112219 is a medium-severity vulnerability in Unknown Download Monitor, published on 23 Oct 2026. 

### Official description

The Download Monitor WordPress plugin before 5.3.5 does not correctly restrict management of the list of filesystem locations it may serve files from to network administrators on multisite, allowing a subsite administrator who is not trusted at the network level to approve arbitrary locations and have the Download Monitor WordPress plugin before 5.3.5 serve readable files from outside the uploads directory, including files belonging to other subsites, to unauthenticated visitors; single-site installations are unaffected.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-112219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112219 is a medium-severity vulnerability in Unknown Download Monitor, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112219 in the wild and no public exploit code.

Affected product: Unknown Download Monitor. 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-112219/ (Markdown: https://insights.sbomify.com/CVE-2026-112219/index.md)
```

## Sources

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

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