dbcve.org
Wp DownloadmanagerWordPress extension · Wp Downloadmanager Project

CVE-2022-25606

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-25
Fix available
A fix is available. Upgrade to 1.68.6 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
Multiple Authenticated Stored Cross-Site Scripting (XSS) vulnerabilities discovered in WP-DownloadManager WordPress plugin (versions <= 1.68.6). Vulnerable parameters &download_path, &download_path_url, &download_page_url, &download_categories.

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 stored XSS vulnerability in WP-DownloadManager plugin allows attackers with contributor-level or higher access to inject malicious JavaScript via four parameters (download_path, download_path_url, download_page_url, download_categories). The injected payloads persist in the database and execute when other users view affected pages.

MitigationUpdate WP-DownloadManager to version 1.68.7 or later which contains the security patch. Until then, restrict administrative access and review user permissions.

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.6

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
    Navigate to WordPress Admin > Plugins and look for 'WP-DownloadManager' in the installed plugins list, or check for the plugin directory at wp-content/plugins/wp-downloadmanager/ via file system access
    Affected if WP-DownloadManager plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress Admin > Plugins, find WP-DownloadManager and view the version number displayed below the plugin name, or open the main plugin file (usually downloadmanager.php) and look for the 'Version:' header in the plugin comment block
    Affected if The version number is less than 1.68.6 (for example, 1.68.5, 1.67.x, etc.)
  3. Identify users with contributor-level or higher access
    In WordPress Admin > Users, review the role column for each user account. Contributor, Author, Editor, and Administrator roles all have access sufficient to trigger the vulnerability
    Affected if There exist one or more users with Contributor, Author, Editor, or Administrator role who can access the plugin's download management features
  4. Inspect database for suspicious entries in affected fields
    Query the WordPress database table (typically wp_downloadmanager or similar, depending on prefix) and examine the download_path, download_path_url, download_page_url, and download_categories columns for unusual script tags, javascript: prefixes, or encoded payloads
    Affected if Any records contain HTML script tags, event handlers (onclick, onerror, etc.), or javascript: URIs in the four affected parameters

A user is affected if WP-DownloadManager version is below 1.68.6 AND the plugin is active with users having contributor-level or higher access, or if malicious payloads already exist in the download-related database 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 1.68.6 or later
Fixed in 1.68.6
Interim mitigation

Update WP-DownloadManager to version 1.68.7 or later which contains the security patch. Until then, restrict administrative access and review user permissions.

Recommended fix High confidence

1.68.6 or later

  1. Back up your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find WP-DownloadManager in the plugin list
  5. If an update is available, click 'Update Now' to upgrade to version 1.68.6 or later
  6. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  7. Verify the update was successful by checking the plugin version

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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