The Brizy Page Builder plugin <= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with "../" to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.
References
Link | Resource |
---|---|
https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-builder-plugin-allow-site-takeover/ | Third Party Advisory |
https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-builder-plugin-allow-site-takeover/ | Third Party Advisory |
Configurations
History
21 Nov 2024, 06:16
Type | Values Removed | Values Added |
---|---|---|
References | () https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-builder-plugin-allow-site-takeover/ - Third Party Advisory |
Information
Published : 2021-10-14 16:15
Updated : 2024-11-21 06:16
NVD link : CVE-2021-38346
Mitre link : CVE-2021-38346
CVE.ORG link : CVE-2021-38346
JSON object : View
Products Affected
brizy
- brizy-page_builder