{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-2087 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-2087 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2087 is a high-severity cross-site scripting vulnerability in themefusecom Brizy – Page Builder, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-2087 and fix it if it is affected.\n\nWhat it is: CVE-2024-2087 is a high-severity cross-site scripting vulnerability in themefusecom Brizy – Page Builder, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-2087 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-2087/ (Markdown: https://insights.sbomify.com/CVE-2024-2087/index.md)","id":"CVE-2024-2087","markdown":"https://insights.sbomify.com/CVE-2024-2087/index.md","name":"CVE-2024-2087","record":{"aliases":["GHSA-5cfq-mh36-cvhr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary web scripts via form names, leading to script execution when users view the page.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"brizy","vendor":"brizy"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Brizy – Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the form name values in all versions up to, and including, 2.4.43 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","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 - Unauthenticated Stored Cross-Site Scripting via Form","id":"CVE-2024-2087","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"NextScripts: Social Networks Auto-Poster \u003c= 4.4.3 - Authenticated(Subscriber+) Sensitive Information Exposure","id":"CVE-2024-2088"},"packages":[],"prev":{"headline":"Integrate Google Drive \u003c= 1.3.8 - Missing Authorization to Unauthenticated Settings Modification and Export","id":"CVE-2024-2086"},"products":["Brizy – Page Builder"],"published":"2024-06-05","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.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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["themefusecom"]},"summary":"Unauthenticated attackers can inject arbitrary web scripts via form names, leading to script execution when users view the page.","url":"https://insights.sbomify.com/CVE-2024-2087/"}