dbcve.org
Essential BlocksWordPress extension · Wpdeveloper

CVE-2024-31306

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-07
Fix available
A fix is available. Upgrade to 4.5.4 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 WPDeveloper Essential Blocks for Gutenberg allows Stored XSS.This issue affects Essential Blocks for Gutenberg: from n/a through 4.5.3.

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

Stored Cross-site Scripting (XSS) vulnerability in WPDeveloper's Essential Blocks for Gutenberg plugin allows authenticated attackers with contributor-level or higher privileges to inject malicious JavaScript scripts through plugin blocks. The injected scripts persist in the database and execute when other users view the affected content.

MitigationUpdate Essential Blocks for Gutenberg to the latest version (4.5.4 or later) to patch the input sanitization flaw. Until patched, implement Content Security Policy (CSP) headers and consider disabling the affected plugin or adding a WAF rule.

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
Essential BlocksWordPress extension
Affected:< 4.5.4

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. Verify Essential Blocks plugin is installed
    Go to WordPress admin > Plugins and look for 'Essential Blocks for Gutenberg' in the installed plugins list
    Affected if Plugin is installed and active
  2. Check installed version number
    In Plugins list, click on 'Essential Blocks' to view the plugin details, or check the plugin files in /wp-content/plugins/essential-blocks/ for the version in the main PHP file header
    Affected if Version is lower than 4.5.4 (e.g., 4.5.3, 4.5.0, etc.)
  3. Identify posts using Essential Blocks
    Search post content in WordPress database or use WP-CLI: wp post list --post_type=post,page --format=ids | xargs -I {} wp post meta list {} | grep _Essential_Blocks or inspect posts in Gutenberg editor for blocks from this plugin
    Affected if Posts or pages contain content created with Essential Blocks plugin
  4. Inspect database for suspicious script tags
    Query the wp_posts table for any <script> tags or JavaScript event handlers (onload, onerror, onmouseover, etc.) in post_content: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%'
    Affected if Database contains posts with embedded script tags or javascript: URIs that were injected

You are affected if Essential Blocks plugin is installed with version below 4.5.4 AND your site has content created using the plugin that may contain injected malicious scripts.

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 4.5.4 or later
Fixed in 4.5.4
Interim mitigation

Update Essential Blocks for Gutenberg to the latest version (4.5.4 or later) to patch the input sanitization flaw. Until patched, implement Content Security Policy (CSP) headers and consider disabling the affected plugin or adding a WAF rule.

Recommended fix Moderate confidence

Essential Blocks for Gutenberg version 4.5.4

  1. Backup your WordPress site database and files before updating
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate Essential Blocks for Gutenberg in the plugin list
  4. Click 'Update now' on the Essential Blocks plugin (or update via WordPress Updates if shown)
  5. Confirm the update to version 4.5.4 was successful
  6. Clear any caching plugins or server-side caches
  7. Test the site frontend and Gutenberg editor functionality to ensure the plugin works correctly

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

Fix this in Essential Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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