dbcve.org
Download ManagerWordPress extension · W3eden

CVE-2024-29114

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 3.2.85 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in W3 Eden, Inc. Download Manager allows Stored XSS.This issue affects Download Manager: from n/a through 3.2.84.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in W3 Eden's Download Manager plugin allows authenticated attackers to inject malicious JavaScript code through plugin input fields. The payload is stored and executed when other users access affected pages, potentially leading to session hijacking or credential theft.

MitigationUpgrade to the latest version of Download Manager beyond 3.2.84, which should contain the patched version with proper input sanitization. Implement output encoding on all user-controlled data before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Download ManagerWordPress extension
Affected:< 3.2.85

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Download Manager plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Download Manager' by W3 Eden, or check the filesystem under wp-content/plugins/download-manager
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, go to Plugins > Download Manager and view the version number displayed, or inspect the main plugin file (download-manager.php) for the 'Version' header comment
    Affected if The version is below 3.2.85 (e.g., 3.2.84, 3.2.80, etc.)
  3. Verify plugin is active
    Check the Plugins page status in WordPress admin - the plugin must be activated for the XSS to be exploitable
    Affected if The plugin status shows as 'Active'
  4. Inspect plugin input fields for suspicious content
    Access the Download Manager settings pages (Downloads > Add New, or Settings > Download Manager) and examine text input fields, meta fields, or file description fields. View the page source or inspect database entries in wp_posts or wp_postmeta for the _wpdm_settings or similar meta keys containing script tags
    Affected if JavaScript tags (<script>), event handlers (onload=, onerror=), or encoded payloads are found in plugin-stored data
  5. Check user access to plugin settings
    Review WordPress user roles with access to Download Manager admin pages. Go to Users > All Users and check which roles have manage_options or plugin-specific capabilities
    Affected if Multiple non-admin users have write access to plugin input fields (contributor, author, or editor roles with plugin access)

You are affected if the Download Manager plugin is active with version below 3.2.85 and any unescaped user-supplied content exists in plugin settings or download metadata fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.85 or later
Fixed in 3.2.85
Interim mitigation

Upgrade to the latest version of Download Manager beyond 3.2.84, which should contain the patched version with proper input sanitization. Implement output encoding on all user-controlled data before rendering.

Recommended fix Moderate confidence

Download Manager version 3.2.85

  1. Backup your WordPress database and files before proceeding
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find 'Download Manager' in the plugin list
  5. If an update is available, click 'Update Now' to upgrade to version 3.2.85 or later
  6. Alternatively, download version 3.2.85 or latest from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  7. Verify the plugin version shows 3.2.85 or higher after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Download Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29114 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data