# CVE-2026-2419: Path traversal in WP-DownloadManager

> Authenticated administrators can exploit path traversal in WP-DownloadManager to read arbitrary files on the server.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q7wp-4j7p-g4vj

## What is CVE-2026-2419?

CVE-2026-2419 is a low-severity path traversal vulnerability in gamerz WP-DownloadManager, published on 18 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP-DownloadManager plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.69 via the 'download_path' configuration parameter. This is due to insufficient validation of the download path setting, which allows directory traversal sequences to bypass the WP_CONTENT_DIR prefix check. This makes it possible for authenticated attackers, with Administrator-level access and above, to configure the plugin to list and access arbitrary files on the server by exploiting the file browser functionality.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-2419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2419 is a low-severity path traversal vulnerability in gamerz WP-DownloadManager, published on 18 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2419 in the wild and no public exploit code.

Affected product: gamerz WP-DownloadManager. 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-2419/ (Markdown: https://insights.sbomify.com/CVE-2026-2419/index.md)
```

## Sources

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

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