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

CVE-2026-14343

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-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 6 weeks old

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 'note_before' and 'note_after' Shortcode Attributes in all versions up to, and including, 3.3.61 due to insufficient input sanitization and output escaping. 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 an injected page. Because wp_kses_post filters post content on save for users without unfiltered_html, only kses-allowed tag and attribute payloads that survive save-time filtering will reach the unescaped sink; however, the sink itself remains unsafe and such payloads can still execute in the browser when a user renders the shortcode.

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 WordPress plugin fails to properly sanitize and escape output for the 'note_before' and 'note_after' shortcode attributes. Authenticated attackers with contributor-level permissions can inject malicious scripts via these attributes that persist in the database and execute when users view affected pages. While wp_kses_post filters some dangerous content at save time, the output sink remains unescaped, allowing certain payloads to execute in browsers.

MitigationUpdate the Download Manager plugin to a version beyond 3.3.61 that includes proper input sanitization and output escaping for shortcode attributes. Alternatively, remove shortcode usage from untrusted content or restrict contributor-level access.

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. Confirm Download Manager plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Download Manager' in the plugin list.
    Affected if The Download Manager plugin appears in the installed plugins list.
  2. Check the installed plugin version
    In the Plugins list, locate Download Manager and note the version number displayed below the plugin name. Compare this to the affected range (versions prior to 3.3.61).
    Affected if The installed version is earlier than 3.3.61.
  3. Identify shortcode usage with vulnerable attributes
    Search posts, pages, and custom post types for the shortcode [download_manager] containing 'note_before=' or 'note_after=' attributes. Use database query: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[download_manager%note_before=%' OR post_content LIKE '%[download_manager%note_after=%'; (adjust wp_ prefix if custom).
    Affected if Any posts or pages contain the download-manager shortcode with note_before or note_after attributes.
  4. Inspect attribute values for unsanitized content
    Examine the values assigned to note_before and note_after in the identified shortcodes. Look for script tags, event handlers (onclick, onerror, onload), or other JavaScript code.
    Affected if The note_before or note_after values contain raw HTML, script tags, or JavaScript event handlers without proper escaping.

A user is affected if the Download Manager plugin version is earlier than 3.3.61 AND any published content contains the download-manager shortcode with note_before or note_after attributes that include unsanitized script content.

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.61 that includes proper input sanitization and output escaping for shortcode attributes. Alternatively, remove shortcode usage from untrusted content or restrict contributor-level access.

Recommended fix Moderate confidence

Version 3.3.62 or later (any version newer than 3.3.61)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate the 'Download Manager' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/download-manager/ and upload it manually
  6. 6. After updating, verify the plugin is running version 3.3.62 or later
  7. 7. Test that the shortcode functionality still works correctly with the note_before and note_after attributes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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