CVE-2026-2571

Download Manager <= 3.3.49 - Missing Authorization to Authenticated (Subscriber+) User Email Enumeration via 'user' Parameter

2026-03-18 00:00
Quốc Huy (jtwings)

Strategic Overview

Status
Patched in 3.3.50
Affected Plugin
Download Manager
Affected Version
<= 3.3.49
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-2571
View all Download Manager vulnerabilities

At a glance

CVE-2026-2571 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Download Manager WordPress plugin, affecting versions <= 3.3.49. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.50; sites on affected versions should update now. Disclosed March 2026, reported by Quốc Huy (jtwings).

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

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

Download Manager <= 3.3.49 carries this weakness at reviewUserStatus, and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Download Manager the fix is 3.3.50: builds <= 3.3.49 are affected, anything from 3.3.50 onward is not.

Remediation

Update to version 3.3.50, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Download Manager 3.3.50 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C