# CVE-2026-2571: Missing authorization in Download Manager

> Authenticated subscribers can enumerate user emails and personal data due to missing capability checks in the Download Manager plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-94v4-f8fh-fgp2

## What is CVE-2026-2571?

CVE-2026-2571 is a medium-severity missing authorization vulnerability in codename065 Download Manager, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Download Manager plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'reviewUserStatus' function in all versions up to, and including, 3.3.49. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive information for any user on the site including email addresses, display names, and registration dates.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-2571 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2571 is a medium-severity missing authorization vulnerability in codename065 Download Manager, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2571 in the wild and no public exploit code.

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

## Sources

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

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