dbcve.org
Download ManagerWordPress extension · W3eden

CVE-2022-36288

HIGH · 8.8 CVSS v3.1 Published 2022-08-23
Fix available
A fix is available. Upgrade to after 3.2.48 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cross-Site Request Forgery (CSRF) vulnerabilities in W3 Eden Download Manager plugin <= 3.2.48 at WordPress.

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

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities exist in the W3 Eden Download Manager WordPress plugin versions 3.2.48 and below. These vulnerabilities allow attackers to trick authenticated administrators into performing unintended state-changing actions (such as modifying plugin settings, manipulating downloads, or altering user permissions) via maliciously crafted requests.

MitigationUpdate the Download Manager plugin to a version beyond 3.2.48 and implement WordPress nonces (anti-CSRF tokens) for all state-changing operations including form submissions and AJAX actions.

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

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 plugin version installed
    In WordPress admin, go to Plugins > Installed Plugins > Download Manager and check the version number displayed. Alternatively, inspect the main plugin file (usually wp-content/plugins/download-manager/include/functions.php or similar) and look for a version constant or comment header.
    Affected if The displayed version is 3.2.48 or lower.
  2. Inspect plugin for nonce implementation
    Examine the main plugin PHP files for presence of WordPress nonce functions. Search for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'check_ajax_referer' in the plugin directory. Use grep or a text editor to scan all PHP files in the download-manager folder.
    Affected if State-changing functions (settings save, user permission changes, download manipulation) lack nonce verification calls.
  3. Check admin action handlers for referer validation
    Look at PHP files handling POST and GET requests that modify plugin settings or user data. Identify functions that process form submissions or AJAX requests. Verify if they validate the request origin using check_admin_referer or similar.
    Affected if Admin action handlers accept requests without validating nonce tokens or request referer.
  4. Review form submission endpoints
    Locate HTML forms in the plugin admin pages (settings pages, package editor, user permission pages). Inspect the HTML source to see if each form includes a hidden nonce field. Check forms in wp-admin for any state-changing operations.
    Affected if Forms modifying settings, packages, or permissions do not contain wp_nonce_field output.
  5. Check AJAX action handlers
    Find all admin-ajax.php hooks registered by the plugin (look for 'wp_ajax_' add_action calls). Verify each handler validates a nonce before processing. Search for 'add_action' calls in plugin files and trace the corresponding handler functions.
    Affected if AJAX handlers that modify data (create/update/delete packages, change user access) lack nonce validation.

You are affected if the installed Download Manager version is 3.2.48 or lower AND state-changing operations (settings saves, package edits, permission changes) in the plugin lack WordPress nonce verification.

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.

From vendor data
Upgrade available Upgrade to a release after 3.2.48
Interim mitigation

Update the Download Manager plugin to a version beyond 3.2.48 and implement WordPress nonces (anti-CSRF tokens) for all state-changing operations including form submissions and AJAX actions.

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-2022-36288 — 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-36288 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