{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3711 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3711 is a medium-severity missing authorization vulnerability in themefusecom Brizy – Page Builder, published on 23 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3711 and fix it if it is affected.\n\nWhat it is: CVE-2024-3711 is a medium-severity missing authorization vulnerability in themefusecom Brizy – Page Builder, published on 23 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-3711 in the wild and no public exploit code.\n\nAffected product: themefusecom 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-2024-3711/ (Markdown: https://insights.sbomify.com/CVE-2024-3711/index.md)","id":"CVE-2024-3711","markdown":"https://insights.sbomify.com/CVE-2024-3711/index.md","name":"CVE-2024-3711","record":{"aliases":["GHSA-72pg-72hh-vvpx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can modify Brizy Page Builder settings and templates due to missing capability checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"brizy","vendor":"brizy"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Brizy – Page Builder plugin for WordPress is vulnerable to unauthorized plugin setting update due to a missing capability check on the functions action_request_disable, action_change_template, and action_request_enable in all versions up to, and including, 2.4.43. This makes it possible for authenticated attackers, with contributor access or above, to enable/disable the Brizy editor and modify the template used.","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 – Page Builder \u003c= 2.4.43 - Missing Authorization","id":"CVE-2024-3711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"GiveWP – Donation Plugin and Fundraising Platform \u003c= 3.10.0 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-3714"},"packages":[],"prev":{"headline":"Image Photo Gallery Final Tiles Grid \u003c 3.6.0 - Contributor+ Stored XSS","id":"CVE-2024-3710"},"products":["Brizy – Page Builder"],"published":"2024-05-23","related":[{"cvss_score":9.9,"headline":"Brizy – Page Builder \u003c= 2.6.4 - Authenticated (Contributor+) Arbitrary File Upload via storeUploads","id":"CVE-2024-10960","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":8.8,"headline":"Brizy – Page Builder \u003c= 2.4.44 - Authenticated (Contributor+) Arbitrary File Upload","id":"CVE-2024-3242","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":8.8,"headline":"Brizy – Page Builder \u003c= 2.4.40 - Authenticated (Contributor+) Arbitrary File Upload","id":"CVE-2024-1311","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":7.4,"headline":"Brizy – Page Builder \u003c= 2.4.43 - Authenticated (Contributor+) Store Cross-Site Scripting via Widget Link To URL","id":"CVE-2024-3667","kev_date_added":null,"published":"2024-06-05"},{"cvss_score":7.4,"headline":"Brizy \u003c 1.0.126 - Authorization Bypass to Settings Updates","id":"CVE-2020-36714","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.2,"headline":"Brizy – Page Builder \u003c= 2.4.43 - Unauthenticated Stored Cross-Site Scripting via Form","id":"CVE-2024-2087","kev_date_added":null,"published":"2024-06-05"},{"cvss_score":7.1,"headline":"WordPress Brizy Pro Plugin \u003c= 2.6.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-22763","kev_date_added":null,"published":"2025-01-21"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["themefusecom"]},"summary":"Authenticated contributors can modify Brizy Page Builder settings and templates due to missing capability checks.","url":"https://insights.sbomify.com/CVE-2024-3711/"}