dbcve.org
Page Builder SandwichWordPress extension · Pagebuildersandwich

CVE-2024-37219

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to after 5.1.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 (XSS or 'Cross-site Scripting') vulnerability in PBN Hosting SL Page Builder Sandwich – Front-End Page Builder allows Stored XSS.This issue affects Page Builder Sandwich – Front-End Page Builder: from n/a through 5.1.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 · high confidence

Stored XSS vulnerability in Page Builder Sandwich plugin allows attackers to inject malicious JavaScript through unsanitized input that gets stored in the database and executed when other users view affected pages.

MitigationImplement proper input sanitization using WordPress sanitization functions and output encoding for all user-supplied data before rendering; apply Content Security Policy headers as defense-in-depth.

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
Page Builder SandwichWordPress extension
Affected:<= 5.1.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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Pagebuildersandwich Page Builder Sandwich', and note the version number displayed
    Affected if Plugin version is 5.1.0 or lower
  2. Identify accessible input fields
    Access the Page Builder Sandwich editor interface and identify any user-supplied input fields (text inputs, content fields, custom fields) where data can be entered and saved
    Affected if Untrusted users can access and submit input through the plugin's frontend or admin forms
  3. Query database for stored scripts
    Inspect WordPress database tables (typically wp_posts, wp_postmeta, or plugin-specific tables) for stored entries containing script tags, javascript:, or onload/onerror event handlers within plugin-related content
    Affected if Database contains any script tags or malicious JavaScript in fields associated with the plugin
  4. Verify output encoding status
    Examine page source code when viewing pages built with the plugin; check if user-supplied content is rendered with proper HTML entity encoding or is output raw
    Affected if User input appears unescaped in HTML output (visible script tags, unencoded < > characters)

If the Page Builder Sandwich plugin version is 5.1.0 or lower AND untrusted users can submit input through the plugin AND that input is stored and rendered without encoding, the environment is affected by this stored XSS vulnerability.

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 a release after 5.1.0
Interim mitigation

Implement proper input sanitization using WordPress sanitization functions and output encoding for all user-supplied data before rendering; apply Content Security Policy headers as defense-in-depth.

Recommended fix Moderate confidence

Upgrade to the latest available version of Page Builder Sandwich (version after 5.1.0) which contains the security patch for CVE-2024-37219

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Page Builder Sandwich' in the plugin list
  4. 4. Check the current installed version (should be <= 5.1.0)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version which contains the security fix for this stored XSS vulnerability
  6. 6. Alternatively, download the latest version from the WordPress Plugin Repository or the vendor's official source and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is functioning correctly and test that the XSS vulnerability is no longer exploitable
Caveat Review plugin settings and frontend pages after update to ensure custom configurations and page builder content render correctly

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

Fix this in Page Builder Sandwich Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-37219 — 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-37219 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