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.
References
Link | Resource |
---|---|
https://wpscan.com/vulnerability/c20e243d-b0de-4ae5-9a0d-b9d02c9b8141 | Exploit Third Party Advisory |
https://www.themeum.com/wp-page-builder-updated-v1-2-4/ | Patch Vendor Advisory |
Configurations
Information
Published : 2021-04-05 12:15
Updated : 2021-04-12 06:10
NVD link : CVE-2021-24208
Mitre link : CVE-2021-24208
JSON object : View
CWE
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Products Affected
themeum
- wp_page_builder