Gutenberg Blocks For Wordpress Download ManagerWordPress extension · Wpdownloadmanager
CVE-2023-22713
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 · uneditedAuth. (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress Download Manager Gutenberg Blocks by WordPress Download Manager plugin <= 2.1.8 versions.
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 confidenceAn authenticated Cross-Site Scripting (XSS) vulnerability in WordPress Download Manager Gutenberg Blocks plugin versions 2.1.8 and below allows users with contributor-level or higher permissions to inject malicious JavaScript through plugin parameters, which executes in the browsers of other users viewing affected content.
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
Gutenberg Blocks For Wordpress Download ManagerWordPress extension
< 2.1.9CVSS 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.
-
Locate the Gutenberg Blocks plugin in WordPressNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Gutenberg Blocks For Wordpress Download Manager' or 'wpdownloadmanager'Affected if The plugin is present in the plugins list
-
Determine the installed plugin versionIn the Plugins list, click on the plugin name to view details, or look at the version number displayed in the plugin listAffected if The version listed is 2.1.8 or below (less than 2.1.9)
-
Confirm the plugin is activeIn the Plugins list, verify the plugin status shows 'Active' under the plugin nameAffected if The plugin is currently active and being used on the site
-
Verify user role accessCheck WordPress user roles at Users > All Users to identify accounts with Contributor, Author, Editor, or Administrator rolesAffected if Any user accounts with contributor-level or higher permissions exist on the site (these users could potentially exploit the vulnerability)
A site is affected if the WordPress Download Manager Gutenberg Blocks plugin version 2.1.8 or below is installed and active, with at least one user having contributor-level or higher permissions.
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.
dbcve · scoped2.1.9
Update the WordPress Download Manager Gutenberg Blocks plugin to a version newer than 2.1.8. If no update is available, disable or remove the plugin until a patch is released.
2.1.9 or higher
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Find 'Gutenberg Blocks For WordPress Download Manager'
- 4. Click 'Update now' if an update is available, or manually update to version 2.1.9 or higher
- 5. Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gutenberg Blocks For Wordpress Download Manager
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22713 — 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-2023-22713 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