dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5357

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Download Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sid' parameter of the 'wpdm_members' shortcode in versions up to and including 3.3.52. This is due to insufficient input sanitization and output escaping on the user-supplied 'sid' shortcode attribute. The sid parameter is extracted without sanitization in the members() function and stored via update_post_meta(), then echoed directly into an HTML id attribute in the members.php template without applying esc_attr(). This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected page.

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

The Download Manager plugin for WordPress (versions up to 3.3.52) contains a stored XSS vulnerability in the wpdm_members shortcode. The 'sid' parameter is extracted without sanitization and stored via update_post_meta(), then echoed directly into an HTML id attribute in the members.php template without esc_attr() escaping, allowing authenticated contributors and above to inject malicious scripts.

MitigationUpdate the Download Manager plugin to a version beyond 3.3.52 when available; alternatively, apply sanitize_text_field() to the 'sid' parameter before storage and esc_attr() when echoing in the members.php template.

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

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Download Manager plugin is installed
    Navigate to WordPress Admin > Plugins and confirm the 'Download Manager' plugin is installed and active
    Affected if Plugin is installed and active with version 3.3.52 or lower
  2. Check plugin version number
    In Plugins list, click on 'Download Manager' to view the version details, or check the plugin header in wp-content/plugins/download-manager/plugin.php
    Affected if Version displayed is 3.3.52 or any version lower than 3.3.52
  3. Confirm wpdm_members shortcode usage
    Search the WordPress database or use a plugin to search post content for '[wpdm_members]' shortcode, or check pages where member directories are displayed
    Affected if The shortcode is present and used on any public-facing page
  4. Inspect members.php template for unescaped output
    Locate the members.php template file in the plugin directory (wp-content/plugins/download-manager/templates/members.php) and examine line where 'sid' parameter is echoed into an HTML id attribute
    Affected if The value is output using plain echo or print without esc_attr() wrapping the 'sid' parameter

You are affected if the Download Manager plugin version is 3.3.52 or lower and the wpdm_members shortcode is in use on your site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Download Manager plugin to a version beyond 3.3.52 when available; alternatively, apply sanitize_text_field() to the 'sid' parameter before storage and esc_attr() when echoing in the members.php template.

Recommended fix Moderate confidence

Download Manager plugin version 3.3.53 or later

  1. 1. Log in to the WordPress admin dashboard with contributor-level or higher access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Download Manager' plugin in the plugin list
  4. 4. Check the current version installed (should be 3.3.52 or below)
  5. 5. Click 'Update Now' if an update to version 3.3.53 or later is available, or manually download and install version 3.3.53 or latest stable release from the WordPress plugin repository
  6. 6. After updating, verify the plugin version shows 3.3.53 or higher
  7. 7. Test that the wpdm_members shortcode with the sid parameter now properly sanitizes and escapes input
Caveat No breaking changes expected for this security patch update; this is a routine maintenance release fixing the XSS vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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