Wp DownloadmanagerWordPress extension · Wp Downloadmanager Project
CVE-2022-25605
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 · uneditedMultiple Authenticated Stored Cross-Site Scripting (XSS) vulnerabilities discovered in WP-DownloadManager WordPress plugin (versions <= 1.68.6). Vvulnerable parameters &download_path, &download_path_url, &download_page_url.
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 confidenceThe WP-DownloadManager plugin versions 1.68.6 and below contain authenticated stored XSS vulnerabilities in three parameters: download_path, download_path_url, and download_page_url. An authenticated attacker with contributor-level or higher access can inject malicious scripts that execute when users view download pages.
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
<= 1.68.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP-DownloadManager is installedLocate the plugin in the WordPress wp-content/plugins directory or view it in the WordPress admin under Plugins > Installed PluginsAffected if The WP-DownloadManager plugin files are present on the server
-
Check the installed version numberView the plugin version in the WordPress admin plugin list, or read the main plugin PHP file header for the Version fieldAffected if The version listed is 1.68.6 or lower
-
Confirm the plugin is activeCheck the WordPress admin Plugins page to see if WP-DownloadManager is activatedAffected if The plugin shows as Active
-
Review user accounts with contributor or higher accessGo to WordPress admin Users section and list accounts with Contributor, Author, Editor, or Administrator rolesAffected if There are user accounts with contributor-level or higher privileges, especially unfamiliar or untrusted ones
-
Inspect the affected settings for injected scriptsNavigate to the WP-DownloadManager settings page and examine the fields for Download Path, Download Path URL, and Download Page URL. Also query the wp_options table for option names containing download_path or download_page_urlAffected if Any of these fields contain unexpected script tags, HTML elements, or JavaScript code that was not intentionally added
You are affected if the WP-DownloadManager plugin is installed, active, and running version 1.68.6 or lower, with any user having contributor-level access able to inject scripts into the download_path, download_path_url, or download_page_url parameters.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to WP-DownloadManager version 1.68.7 or later. The fix requires proper input sanitization and output escaping for the affected parameters to prevent script injection.
Fix this in Wp Downloadmanager
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-25605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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