CVE-2025-13498
Unauthorized Access in WordPress Download Manager Plugin Allows Data Exposure
Publication date: 2025-12-18
Last updated on: 2025-12-18
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpres | download_manager | 3.3.32 |
| wordpres | download_manager | 3.3.33 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the WordPress Download Manager plugin (up to version 3.3.32) allows authenticated users with Subscriber-level access or higher to bypass intended media protection. Due to missing authorization and capability checks on the `wpdm_media_access` AJAX action, attackers can retrieve passwords and access control settings for protected media attachments. This enables them to download restricted files that should otherwise be protected. The issue stems from improper validation and enforcement of access controls in the media access control functions, allowing unauthorized access to sensitive media files. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an attacker with low-level authenticated access (Subscriber or above) to obtain passwords and access control settings for protected media files. This can lead to unauthorized downloading of restricted or sensitive media content that should be protected, potentially exposing confidential or private files. The impact is limited to confidentiality loss of protected media files, as the vulnerability does not affect integrity or availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unauthorized access attempts to the `wpdm_media_access` AJAX action in the WordPress Download Manager plugin (version 3.3.32 and earlier). You can look for suspicious AJAX requests that attempt to retrieve media passwords or access control settings without proper authorization. Specifically, inspecting HTTP logs for POST requests to `admin-ajax.php` with the action parameter `wpdm_media_access` from Subscriber-level or lower accounts may indicate exploitation attempts. Additionally, checking for unusual media download activity or access to protected media files can help detect exploitation. Commands to assist detection could include using web server access logs with grep, for example: `grep 'admin-ajax.php' /var/log/apache2/access.log | grep 'wpdm_media_access'` or using network monitoring tools to filter HTTP POST requests containing `wpdm_media_access`. However, no explicit detection commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WordPress Download Manager plugin to version 3.3.33 or later, which contains the fix for CVE-2025-13498. This update corrects the nonce validation logic in the media protection function, preventing unauthorized access via the `wpdm_media_access` AJAX action. Until the update can be applied, consider restricting access to the AJAX action by limiting user roles that can perform media access requests, or disabling the plugin if feasible. Additionally, review and tighten media access control settings and passwords for protected media files. Applying the official patch or update is the most effective and recommended mitigation. [3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to sensitive information such as passwords and access control settings for protected media attachments. This unauthorized access could lead to exposure of protected or confidential data, potentially violating data protection requirements under standards like GDPR or HIPAA. However, the provided resources do not explicitly discuss compliance impacts or regulatory consequences. [1, 3]