CVE-2026-86611 Download Manager (Free & Pro) - Privacy Settings Update via CSRF
Medium 4.3
Published
Updated
Check this codebase for CVE-2026-86611 and fix it if it is affected.
What it is: CVE-2026-86611 is a medium-severity vulnerability in Unknown Download Manager, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-86611 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-86611/ (Markdown: https://insights.sbomify.com/CVE-2026-86611/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-86611?
CVE-2026-86611 is a medium-severity vulnerability in Unknown Download Manager, published on 21 Oct 2026.
Official description
The Download Manager WordPress plugin before 3.3.71, Download Manager WordPress plugin before 7.5.9 does not have CSRF checks in some places, allowing attackers to make a logged in admin update its privacy and storage settings via a crafted link, including the credential that gates its unauthenticated maintenance endpoint.
Weakness: CWE-352
Which versions are affected by CVE-2026-86611?
How do I fix CVE-2026-86611?
No fix has been published for CVE-2026-86611 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-86611 being exploited?
There is no known exploitation of CVE-2026-86611 in the wild and no public exploit code.
Sources
Also known as GHSA-2f6h-f6g2-jxwq.