Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/authenticate as subscriber
-
DeliveryOpen wpdm_edit_profile front-end form
-
ExploitSubmit multiply entity-encoded payload in Display Name
-
ExecutionStored unsanitized, bypassing input filtering
-
PersistAdmin/user views page rendering the name
-
ImpactScript executes in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the plugin's [wpdm_edit_profile] shortcode be present on a front-end page accessible to Subscriber-level users, and that the site permit subscriber-level (or higher) accounts - commonly via open registration. The attacker must authenticate (PR:L, subscriber or above) and submit a multiply entity-encoded payload through the Display Name field to defeat the insufficient sanitization. Realized impact additionally depends on a privileged user (e.g., an administrator viewing download history/stats) subsequently rendering the stored name, which is what makes the scope-change and cross-user compromise meaningful. Limiting factors: no special configuration means NO exploitation - sites without the edit-profile shortcode on a subscriber-reachable page, or with registration disabled, are not exploitable via this path. |
| Impact | This is a moderate-risk, conditionally-exploitable issue rather than a top priority. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) reflects a network-reachable stored XSS requiring only subscriber-level authentication (PR:L), with a scope change (S:C) because injected script executes in the browsers of other users who view the page. No EPSS score, KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the risk here is driven by the plugin's install footprint and the low authentication bar, not by confirmed in-the-wild activity. The signals are internally consistent (no conflict between vector and description), but exploitation is gated by a specific non-default prerequisite: the [wpdm_edit_profile] shortcode must be placed on a front-end page reachable by subscribers. The absence of EPSS/KEV/POC data is a gap in the intelligence set, not a contradiction. Net: a legitimate patch-soon item for sites that expose the edit-profile shortcode and allow open subscriber registration, but low real-world urgency where that shortcode is not deployed. |
| Exploit ScenarioDerived | A site allows open registration and has placed the [wpdm_edit_profile] shortcode on a front-end page; an attacker registers a subscriber account and edits their Display Name to contain a multiply entity-encoded JavaScript payload that evades the plugin's sanitization. When an administrator or other user later views a page rendering that display name (such as download statistics/history views), the script executes in their browser, enabling session or privilege-escalation attacks. No public exploit code was provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Stored cross-site scripting in the Download Manager plugin for WordPress (codename065, all versions up to and including 3.3.70) allows any authenticated user with subscriber-level access or above to persist arbitrary JavaScript through the profile Display Name field, which then executes in the browser of any user - including administrators - who views the affected page or the plugin's download statistics/history screens. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) confirms the attacker must be authenticated (PR:L) but no victim interaction is required beyond rendering the injected content, and the scope change (S:C) reflects cross-privilege execution in the administrative context. Exploitation is strictly conditional: the site must expose the [wpdm_edit_profile] shortcode on a front-end page reachable by Subscriber-level accounts, which in practice usually means open self-registration is enabled; sites lacking that shortcode placement or with registration disabled are not exploitable through this path. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and no EPSS score was supplied, so this should be treated as a moderate, conditionally exploitable issue rather than an urgent one.
RemediationAI
Upstream fix activity is evidenced by the WordPress plugin repository changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3715131%40download-manager&new=3715131%40download-manager, so the primary action is to update the Download Manager plugin past 3.3.70 to the latest available release; note that this is a source/commit-level fix and a specific patched tagged version number could not be independently confirmed from the supplied data, so verify the installed version after updating and re-check the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/e04b75d4-9bf5-4b26-ac3a-88a10d200c50 for the final fixed release. Where updating immediately is not possible, the most effective compensating control is to remove the [wpdm_edit_profile] shortcode from any front-end page reachable by Subscriber-level users (or restrict that page to higher roles), which eliminates the injection vector entirely - the trade-off is loss of front-end profile self-service for those users. Disabling open user registration or lowering the default new-user role removes the ability of unprivileged accounts to submit the payload, at the cost of blocking legitimate sign-ups and requiring manual account provisioning. Administrators should also avoid opening the plugin's download statistics/history screens until patched, since those views are where the stored script renders, and a WAF rule that normalizes multiply entity-encoded input before it reaches the Display Name field can add interim protection, though encoding-based filters are easily bypassed and must be tuned carefully to avoid breaking legitimate names containing HTML entities.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting) in the WordPress Download Manager plugin, a widely deployed file-download and document-management extension. The vulnerable flow begins in src/User/EditProfile.php (referenced at line 57), which handles the front-end profile editor exposed by the [wpdm_edit_profile] shortcode, and in shared sanitization helpers in src/__/__.php (referenced at lines 224 and 300). The Display Name value submitted there is insufficiently sanitized on input and insufficiently escaped on output, so a payload that is multiply entity-encoded (e.g., layered HTML entity encoding) passes through the filter and is decoded/rendered as live markup later. The stored value is subsequently emitted in administrative rendering paths, specifically src/Admin/views/stats/history.php (referenced at lines 232 and 979), which is why the malicious script fires in an administrator's session when download history or statistics are viewed - a classic privileged-context stored XSS. The affected product is identified by CPE cpe:2.3:a:codename065:download_manager:*:*:*:*:*:*:*:* with the advisory tracked as ENISA EUVD-2026-91257 and reported by Wordfence.
Know when Download Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Subscriber account needed so PR:L; network-reachable stored injection (AV:N/AC:L); stored XSS runs in other users' context, so S:C with low C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Download Manager
View allAn issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The Download Manager WordPress plugin before 3.2.83 does not protect file download's passwords, leaking it upon receivin
The basic_settings function in the download manager plugin for WordPress before 2.7.3 allows remote authenticated users
Stored cross-site scripting in the commercial Download Manager Pro WordPress plugin (before version 7.5.6) allows an una
The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion in versions up to, and including 3.2.
Unauth. Rated medium severity (CVSS 6.3), this vulnerability is remotely exploitable, no authentication required, low at
SQL injection vulnerability in download.php in phux Download Manager allows remote attackers to execute arbitrary SQL co
Download Manager WordPress plugin before 3.3.62 fails to bind temporary download tokens to user sessions, creating long-
The Download Manager WordPress plugin before 6.3.0 leaks master key information without the need for a password, allowin
The Download Manager WordPress plugin before 3.2.50 prioritizes getting a visitor's IP from certain HTTP headers over PH
The Download Manager WordPress plugin before 3.2.34 uses the uniqid php function to generate the master key for a downlo
The The Download Manager plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and
EUVD-2026-91257
GHSA-mx7c-775g-f79h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB