Skip to main content
VulnerabilityPublished

CVE-2026-2422: WP Composer – The Easiest Page Builder · Cross-site Scripting

Affects WP Composer – The Easiest Page BuilderSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ghozylabWP Composer – The Easiest Page BuilderAffected
  • <=1.0.5
Fixed in–

AI-suggested

Users should restrict Contributor-level access to trusted users only and consider disabling or removing the WP Composer plugin until a fix is released. Monitor the vendor's advisory channels for updates. Since the vulnerability relies on the shortcode handler's unsafe output of decoded Base64 content, avoid using the 'pbwp_raw_shortcode' shortcode if possible.

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.

References

Community reviews

Loading reviews…