dbcve.org
Page Builder\Application · Blueastral

CVE-2023-52193

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to after 1.5.23 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 Live Composer Team Page Builder: Live Composer allows Stored XSS.This issue affects Page Builder: Live Composer: from n/a through 1.5.23.

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 Page Builder: Live Composer plugin allows authenticated attackers to inject malicious JavaScript through plugin inputs that are not properly sanitized before being rendered in web pages. The vulnerability affects versions through 1.5.23 and can be triggered when a user views a page containing the malicious payload.

MitigationUpdate Page Builder: Live Composer to the latest version if a patched release exists; otherwise, implement proper input sanitization using WordPress sanitization functions (such as esc_html(), esc_attr(), or wp_kses()) on all user-supplied data before output, and consider applying Content Security Policy headers.

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\Application
Affected:<= 1.5.23

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. Identify if Page Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Page Builder: Live Composer' or 'Blueastral Page Builder'. Alternatively, check the wp-content/plugins directory for a folder named 'live-composer' or similar.
    Affected if The plugin is found and active in the WordPress installation
  2. Determine installed version number
    In WordPress admin_plugins list, locate the plugin and read the version number displayed. Alternatively, open the main plugin PHP file (usually in the plugin folder root) and look for the 'Version' header in the plugin comments.
    Affected if Version is 1.5.23 or any lower number
  3. Inspect plugin code for unsanitized output
    Review the plugin PHP files, particularly those handling user input submissions (forms, settings, content builder modules). Look for instances where user-supplied data is output using echo or print without WordPress sanitization functions like esc_html(), esc_attr(), or wp_kses().
    Affected if Code shows raw output of user input without sanitization functions before rendering to page
  4. Examine stored content for malicious payloads
    Check database tables (typically wp_posts or plugin-specific tables) for any stored content containing script tags, javascript: URIs, or on* event handlers. Use a database query or view page source of published builder pages.
    Affected if Stored content contains unsanitized script tags or XSS payloads that execute when pages load

User is affected if Page Builder: Live Composer (Blueastral Page Builder) version 1.5.23 or lower is installed, and the plugin processes user input without proper sanitization before output.

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.

From vendor data
Upgrade available Upgrade to a release after 1.5.23
Interim mitigation

Update Page Builder: Live Composer to the latest version if a patched release exists; otherwise, implement proper input sanitization using WordPress sanitization functions (such as esc_html(), esc_attr(), or wp_kses()) on all user-supplied data before output, and consider applying Content Security Policy headers.

Fix this in Page Builder\ 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-2023-52193 — 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-2023-52193 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