CVE-2026-2422 ghozylab CVE debrief

Who should care

Defenders responsible for WordPress installations with the WP Composer – The Easiest Page Builder plugin, especially those with Contributor-level access and above, should assess exposure and prioritize updates.

Why it matters

Defenders should prioritize verifying and updating the WP Composer – The Easiest Page Builder plugin due to a Stored Cross-Site Scripting vulnerability, which allows authenticated attackers to inject arbitrary web scripts.

• Authenticated attackers with Contributor-level access and above can inject arbitrary web scripts
• Injected scripts can execute whenever a user accesses an injected page
• The vulnerability allows bypassing WordPress's KSES content filtering at save time

Technical summary

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. The vulnerability allows 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. The plugin's failure to properly sanitize

Defensive priority

Defenders should prioritize verifying and updating the WP Composer – The Easiest Page Builder plugin to a version beyond 1.0.5, if available, and assess exposure in their environment.

Recommended defensive actions

• Verify and update the WP Composer – The Easiest Page Builder plugin to a version beyond 1.0.5, if available
• Assess exposure in the environment and prioritize updates for systems with Contributor-level access and above
• Monitor for potential exploitation attempts and review user access controls
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the vendor and affected versions are not clearly stated, requiring further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.