CVE-2026-2422

Received Received - Intake

Stored XSS in WP Composer Page Builder Plugin

Publication date: 2026-09-19

Last updated on: 2026-09-19

Assigner: Wordfence

Description

The WP Composer – The Easiest Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'pbwp_raw_shortcode' shortcode in all versions up to, and including, 1.0.5. This is due to the shortcode handler decoding Base64-encoded content and outputting it directly without any sanitization or escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The Base64 encoding allows the payload to bypass WordPress's KSES content filtering at save time, since the encoded string contains no harmful HTML characters.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-19

Last Modified

2026-09-19

Generated

2026-09-20

AI Q&A

2026-09-20

EPSS Evaluated

N/A

NVD

CVE-2026-2422

Affected Vendors & Products

Vendor	Product	Version / Range
wp_composer	the_easiest_page_builder	to 1.0.5 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-79	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

Executive Summary

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the WP Composer – The Easiest Page Builder plugin for WordPress. It affects versions up to and including 1.0.5. The flaw exists in the 'pbwp_raw_shortcode' shortcode handler, which decodes Base64-encoded content and outputs it without sanitization or escaping. This allows authenticated attackers with Contributor-level access or higher to inject malicious scripts into pages.

Detection Guidance

This vulnerability can be detected by checking for the presence of the WP Composer plugin versions up to and including 1.0.5. Inspect WordPress installations for the plugin and verify its version. Look for suspicious Base64-encoded content in posts or pages that may indicate exploitation attempts.

Impact Analysis

An attacker could exploit this to inject arbitrary web scripts into pages. When users access these pages, the injected scripts execute, potentially stealing user data, session cookies, or performing actions on behalf of the user. The Base64 encoding bypasses WordPress's content filtering, making the attack more stealthy.

Compliance Impact

This vulnerability could lead to data breaches, compromising personal or sensitive data. For GDPR, it may result in unauthorized access to user data, violating principles of data protection and user consent. For HIPAA, it could expose protected health information, leading to compliance violations and legal consequences.

Mitigation Strategies

Immediately update the WP Composer plugin to the latest version if available. If no update exists, consider disabling or removing the plugin until a patch is released. Review all posts and pages for unauthorized scripts, especially those containing Base64-encoded content.

Hi! I’m here to help you understand CVE-2026-2422. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70