First published: Mon Apr 05 2021(Updated: )
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.
Credit: contact@wpscan.com
Affected Software | Affected Version | How to fix |
---|---|---|
Themeum Wp Page Builder | <1.2.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability severity of CVE-2021-24208 is medium with a CVSS score of 5.4.
The WP Page Builder WordPress plugin versions up to (but excluding) 1.2.4 are affected by CVE-2021-24208.
Lower-privileged users can exploit CVE-2021-24208 by inserting unfiltered HTML, including JavaScript, into pages using the "Raw HTML" widget and the "Custom HTML" widget.
Yes, a fix is available for CVE-2021-24208 in version 1.2.4 of the WP Page Builder WordPress plugin.
You can find more information about CVE-2021-24208 at the following references: [Reference 1](https://wpscan.com/vulnerability/c20e243d-b0de-4ae5-9a0d-b9d02c9b8141) and [Reference 2](https://www.themeum.com/wp-page-builder-updated-v1-2-4/).