dbcve.org
Liquid BlocksWordPress extension · Lqd

CVE-2024-52357

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-11
Fix available
A fix is available. Upgrade to 1.3.0 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 lqd LIQUID BLOCKS liquid-blocks allows Stored XSS.This issue affects LIQUID BLOCKS: from n/a through <= 1.2.0.

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

A stored Cross-site Scripting (XSS) vulnerability exists in the LIQUID BLOCKS plugin (versions up to 1.2.0) where user-supplied input is not properly sanitized before being stored and rendered in web pages, allowing malicious JavaScript to execute in the browsers of users who view the affected content.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data rendered in the plugin's front-end, using WordPress sanitization functions like sanitize_text_field() for input and appropriate escaping functions like esc_html() or esc_attr() for output.

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
Liquid BlocksWordPress extension
Affected:< 1.3.0

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. Check the installed LIQUID BLOCKS plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate LIQUID BLOCKS (Lqd Liquid Blocks), or inspect the plugin header in the main plugin file (typically in /wp-content/plugins/liquid-blocks/ or similar path containing 'liquid-blocks')
    Affected if The installed version is 1.2.0 or lower (anything below 1.3.0)
  2. Identify plugin user input forms
    Review the LIQUID BLOCKS plugin settings pages in the WordPress admin for any input fields that accept user-supplied content (such as text inputs, textareas, or custom fields used for block content)
    Affected if The plugin has user-editable input fields where custom content can be entered and saved
  3. Inspect stored data for unsanitized content
    Query the WordPress database (wp_postmeta or relevant custom tables) for any metadata or content stored by the LIQUID BLOCKS plugin that may contain raw HTML or script tags
    Affected if Stored plugin data contains raw, unescaped HTML or JavaScript that was not sanitized on input
  4. View plugin output on front-end pages
    Visit pages or posts using LIQUID BLOCKS blocks and view the page source to inspect how user-supplied content is rendered
    Affected if The plugin outputs user content without proper HTML encoding or escaping (e.g., raw script tags, unescaped HTML attributes)

You are affected if the LIQUID BLOCKS plugin version is below 1.3.0 and the plugin stores and displays user-supplied input without sanitization.

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

Implement proper input validation and output encoding/escaping for all user-supplied data rendered in the plugin's front-end, using WordPress sanitization functions like sanitize_text_field() for input and appropriate escaping functions like esc_html() or esc_attr() for output.

Recommended fix High confidence

1.3.0

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Liquid Blocks' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 1.3.0
  5. Alternatively, you can manually update by downloading version 1.3.0 from the WordPress plugin repository and uploading it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 1.3.0 or higher

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

Fix this in Liquid Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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