CVE-2026-16685

The Download Manager plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'REFERRER' parameter in all versions up to and including 3.3.57 due to insufficient input sanitization and output escaping. An unauthenticated attacker can inject arbitrary web scripts that execute in a victim's browser.

The Download Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'not_found' parameter in all versions up to and including 3.3.58 due to insufficient input sanitization and output escaping. This allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts that execute whenever a user accesses an injected page.

The Download Manager plugin for WordPress up to version 3.3.71 is vulnerable to sensitive information exposure via the 'first_name' parameter. Authenticated attackers with subscriber-level access can extract the administrator's full Cookie header, including wordpress_logged_in_* session cookies, from the suspension email sent during the administrator's authenticated request. This enables full session hijack and account takeover.

The Download Manager plugin for WordPress up to version 3.3.71 is vulnerable to Stored Cross-Site Scripting via the 'regurl' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access can inject arbitrary web scripts that execute when a user accesses an injected page. The injected payload only fires for logged-out visitors, as the vulnerable login-form.php template branch is gated on !is_user_logged_in().

The Download Manager plugin (up to version 3.3.71) has an Authorization Bypass Through User-Controlled Key vulnerability, allowing retrieval of embedded sensitive data. An attacker can exploit a user-controlled key to bypass authorization.

The Download Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Display Name in all versions up to, and including, 3.3.70 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the [wpdm_edit_profile] shortcode to be present on a front-end page accessible to Subscriber-level users, who can then submit a multiply entity-encoded payload via the display name field to bypass sanitization.

The Download Manager WordPress plugin before 7.5.6 does not sanitise and escape data submitted through its email-locked download subscription form before outputting it back in an admin page, which could allow unauthenticated attackers to perform Stored Cross-Site Scripting attacks against administrators. This affects the commercial Pro edition only; the free Download Manager WordPress plugin before 7.5.6 published under the same slug does not ship the affected feature.

The Download Manager plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to and including 3.3.68 via the duplicate() function hooked on admin_init. This is due to the handler only verifying the generic 'edit_posts' capability and a plugin-wide static nonce without any object-level authorization check. Authenticated attackers with Author-level access or above can duplicate arbitrary Download Manager packages owned by other users, copying all package metadata including protected file references, role-based access restrictions, and password lock settings into an attacker-owned clone.

The Download Manager WordPress plugin before version 3.3.66 does not properly escape a package's title before outputting it in front-end templates. Users with the Author role or higher can store a title that results in arbitrary JavaScript execution in the browser of any user, including unauthenticated visitors, who views a page displaying the package.

The Download Manager plugin for WordPress up to version 3.3.61 inclusive is vulnerable to Stored Cross-Site Scripting via 'note_before' and 'note_after' shortcode attributes due to insufficient input sanitization and output escaping.