# CVE-2026-86610: Download Manager < 3.3.71 - Author+ Stored XSS via Package Icon


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-gqp8-r2j3-gh4p

## What is CVE-2026-86610?

CVE-2026-86610 is a medium-severity vulnerability in Unknown Download Manager, published on 1 Oct 2026. 

### Official description

The Download Manager WordPress plugin before 3.3.71 does not sufficiently sanitise and escape a package setting before outputting it back in a page, which could allow users with the Author role and above to perform Stored Cross-Site Scripting attacks against any visitor who opens the package's download dialogue, including administrators. Only sites running PHP below 8.1 are affected, as the sanitisation applied when the setting is saved does not neutralise single quotes there.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-86610 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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