Radar sectionsDatabase
Check my site
WordPress plugin

WP Page Builder <= 1.2.3 — Multiple Stored Cross-Site scripting

CVE-2021-24208Published · Updated

Action summary

Affected: <1.2.4Update to 1.2.4 or newer

All remediation steps
Severity
High7.4
CVSS
7.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-79 Cross-Site Scripting
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WP Page Builder wp-pagebuilder

  1. Affected< 1.2.4
  2. Patched in1.2.4

Update to 1.2.4 or newer.

You are affected if you run < 1.2.4. Version 1.2.4 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP Page Builder.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 1.2.4, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP Page Builder to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Ram.

The editor of the WP Page Builder WordPress plugin before 1.2.4 allows lower-privileged users to insert unfiltered HTML, including JavaScript, into pages via the “Raw HTML” widget and the “Custom HTML” widgets (though the custom HTML widget requires sending a crafted request - it appears that this widget uses some form of client side validation but not server side validation), all of which are added via the “page_builder_data” parameter when performing the “wppb_page_save” AJAX action. It is also possible to insert malicious JavaScript via the “wppb_page_css” parameter (this can be done by closing out the style tag and opening a script tag) when performing the “wppb_page_save” AJAX action.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP Page Builder

All 4
More vulnerabilities in WP Page Builder
SeverityVulnerabilityCVEPublished
Medium5.5Authenticated (Admin+) Stored Cross-Site Scripting
≤1.2.8No patch available
CVE-2022-3830
Medium6.4Authenticated (Author+) Stored Cross-Site Scripting
≤1.2.6Update to 1.2.7
CVE-2022-40963
Medium5.4Insecure Default to Unauthorized Page Editing
<1.2.4Update to 1.2.4
CVE-2021-24207

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.4

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?