Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Brizy | Brizy-Page Builder | <= 2.3.11 |
Related Weaknesses (CWE)
References
- https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-buThird Party Advisory
- https://www.wordfence.com/blog/2021/10/multiple-vulnerabilities-in-brizy-page-buThird Party Advisory
FAQ
What is CVE-2021-38346?
CVE-2021-38346 is a vulnerability with a CVSS score of 8.8 (HIGH). 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...
How severe is CVE-2021-38346?
CVE-2021-38346 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2021-38346?
Check the references section above for vendor advisories and patch information. Affected products include: Brizy Brizy-Page Builder.