{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-38346 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38346 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38346 is a high-severity vulnerability in Brizy.io Brizy - Page Builder, published on 14 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-38346 and fix it if it is affected.\n\nWhat it is: CVE-2021-38346 is a high-severity vulnerability in Brizy.io Brizy - Page Builder, published on 14 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-38346 in the wild and no public exploit code.\n\nAffected product: Brizy.io Brizy - Page Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-38346/ (Markdown: https://insights.sbomify.com/CVE-2021-38346/index.md)","id":"CVE-2021-38346","markdown":"https://insights.sbomify.com/CVE-2021-38346/index.md","name":"CVE-2021-38346","record":{"aliases":["GHSA-gq9p-f72g-3m6j"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can upload executable files via path traversal and double extensions, potentially achieving remote code execution on vulnerable WordPress sites.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"brizy-page_builder","vendor":"brizy"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Brizy Page Builder plugin \u003c= 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Brizy \u003c= 2.3.11 Authenticated Unrestricted File Upload and Path Traversal","id":"CVE-2021-38346","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Custom Website Data \u003c= 2.2 Reflected Cross-Site Scripting","id":"CVE-2021-38347"},"packages":[],"prev":{"headline":"Brizy \u003c= 1.0.125 and 1.0.127 – 2.3.11 Incorrect authorization checks allowing Post modification","id":"CVE-2021-38345"},"products":["Brizy - Page Builder"],"published":"2021-10-14","related":[{"cvss_score":7.1,"headline":"Brizy \u003c= 1.0.125 and 1.0.127 – 2.3.11 Incorrect authorization checks allowing Post modification","id":"CVE-2021-38345","kev_date_added":null,"published":"2021-10-14"},{"cvss_score":6.4,"headline":"Brizy \u003c= 2.3.11 Authenticated Stored Cross-Site Scripting","id":"CVE-2021-38344","kev_date_added":null,"published":"2021-10-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-14","vendors":["Brizy.io"]},"summary":"Authenticated attackers can upload executable files via path traversal and double extensions, potentially achieving remote code execution on vulnerable WordPress sites.","url":"https://insights.sbomify.com/CVE-2021-38346/"}