dbcve.org
Wp DownloadmanagerWordPress extension · Wp Downloadmanager Project

CVE-2021-44760

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 1.68.7 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
Auth. (admin+) Reflected Cross-Site Scripting (XSS) vulnerability discovered in WP-DownloadManager plugin <= 1.68.6 versions.

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 · high confidence

Authenticated (admin+) reflected Cross-Site Scripting (XSS) vulnerability in WP-DownloadManager plugin versions 1.68.6 and earlier. The vulnerability allows an attacker with admin-level privileges to inject malicious JavaScript through unsanitized parameters, which gets reflected back to the user.

MitigationUpdate WP-DownloadManager plugin to a version newer than 1.68.6. If no patched version is available, disable the plugin until a fix is released.

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
Wp DownloadmanagerWordPress extension
Affected:< 1.68.7

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. Verify WP-DownloadManager plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP-DownloadManager' in the list of active plugins.
    Affected if WP-DownloadManager plugin appears in the installed plugins list.
  2. Check installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find WP-DownloadManager, and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header in wp-content/plugins/wp-downloadmanager/download-manager.php for the 'Version' tag.
    Affected if The installed version is 1.68.6 or earlier (anything below 1.68.7).
  3. Confirm admin-level accounts exist
    Navigate to Users > All Users in WordPress admin panel and review the role assigned to each account. Look for users with 'Administrator' role.
    Affected if At least one user account with Administrator role exists on the WordPress site.
  4. Identify exposure to reflected parameters
    Review plugin settings and URLs within WP-DownloadManager. Look for any admin-facing pages that accept URL parameters (query strings) and reflect them back in the response without sanitization. Common indicators include 's', 'search', or 'order' parameters in download-manager admin pages.
    Affected if URL parameters are used and reflected in admin pages without proper output encoding.

A user is affected if WP-DownloadManager version 1.68.6 or earlier is installed and the site has at least one administrator-level account, allowing the reflected XSS to be triggered through vulnerable parameter handling.

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 1.68.7 or later
Fixed in 1.68.7
Interim mitigation

Update WP-DownloadManager plugin to a version newer than 1.68.6. If no patched version is available, disable the plugin until a fix is released.

Recommended fix High confidence

1.68.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP-DownloadManager plugin
  4. Check if the current version is below 1.68.7
  5. If update available, click 'Update Now' to upgrade to version 1.68.7
  6. Alternatively, navigate to Dashboard > Updates and apply all available updates
  7. Verify the plugin is now running version 1.68.7 or higher

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

Fix this in Wp Downloadmanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44760 — 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-2021-44760 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