dbcve.org
Premium Blocks For GutenburgWordPress extension · Leap13

CVE-2024-37519

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to 2.1.28 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Blocks – Gutenberg Blocks for WordPress premium-blocks-for-gutenberg.This issue affects Premium Blocks – Gutenberg Blocks for WordPress: from n/a through <= 2.1.27.

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

This is a stored Cross-site Scripting (XSS) vulnerability in the Premium Blocks for Gutenberg WordPress plugin (premium-blocks-for-gutenberg). Attackers can inject malicious JavaScript through unsanitized input that gets stored and executed when other users view affected pages. The vulnerability affects versions up to and including 2.1.27.

MitigationUpdate the Premium Blocks for Gutenberg plugin to the latest available version which should contain the XSS fix. If an immediate update is not possible, disable the plugin or implement additional output encoding on the affected Gutenberg blocks.

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
Premium Blocks For GutenburgWordPress extension
Affected:< 2.1.28

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Premium Blocks for Gutenberg plugin
    Navigate to WordPress admin > Plugins and look for 'Premium Blocks for Gutenberg' or 'Leap13 Premium Blocks For Gutenberg' in the installed plugins list
    Affected if The plugin is not installed or not present in the plugins directory
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view its details, or check the plugin files in wp-content/plugins/premium-blocks-for-gutenberg/ for a version marker in the main PHP file or readme.txt
    Affected if The displayed version is 2.1.27 or lower, or no version is displayed and the plugin has not been updated recently
  3. Check if Gutenberg editor blocks are in use
    Edit any WordPress page or post and look for block categories named 'Premium Blocks', 'Leap13', or specific block names from this plugin (Premium Button, Premium Container, Premium Card, etc.) in the Gutenberg block inserter
    Affected if Pages or posts have been edited using the Gutenberg editor with Premium Blocks installed and blocks have been added to content

A user is affected if the Premium Blocks for Gutenberg plugin is installed with version 2.1.27 or lower and Gutenberg blocks from this plugin have been used to create 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
Upgrade available Upgrade to 2.1.28 or later
Fixed in 2.1.28
Interim mitigation

Update the Premium Blocks for Gutenberg plugin to the latest available version which should contain the XSS fix. If an immediate update is not possible, disable the plugin or implement additional output encoding on the affected Gutenberg blocks.

Recommended fix High confidence

Premium Blocks For Gutenberg version 2.1.28 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Premium Blocks For Gutenberg' (or 'Premium Blocks – Gutenberg Blocks for WordPress')
  4. Click 'Update now' if an update is available, or manually update to version 2.1.28 or later
  5. Verify the plugin version after updating to confirm version 2.1.28 or higher is installed

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

Fix this in Premium Blocks For Gutenburg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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