{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5324 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5324 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5324 is a high-severity cross-site scripting vulnerability in themefusecom Brizy – Page Builder, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5324 and fix it if it is affected.\n\nWhat it is: CVE-2026-5324 is a high-severity cross-site scripting vulnerability in themefusecom Brizy – Page Builder, published on 2 May 2026. 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-2026-5324 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-2026-5324/ (Markdown: https://insights.sbomify.com/CVE-2026-5324/index.md)","id":"CVE-2026-5324","markdown":"https://insights.sbomify.com/CVE-2026-5324/index.md","name":"CVE-2026-5324","record":{"aliases":["GHSA-p8xr-fh24-8289"],"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 scripts via form submissions that execute when administrators view the leads page, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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 Unauthenticated Stored Cross-Site Scripting in all versions up to, and including, 2.8.11 This is due to a combination of missing nonce verification for unauthenticated form submissions, insufficient handling of FileUpload fields when no file is uploaded, and the reversal of security encoding via html_entity_decode() followed by unescaped output in the admin view. The submit_form() function skips nonce verification for non-logged-in users (api.php:198). The handleFileTypeFields() function fails to overwrite user-supplied values when no file is attached. While htmlentities() is applied during storage, html_entity_decode() reverses this on display (form-entries.php:79). The form-data.php template outputs FileUpload values directly in href attributes without esc_url(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form Leads 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.8.11 - Unauthenticated Stored Cross-Site Scripting via FileUpload Field Value","id":"CVE-2026-5324","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"SourceCodester Simple Customer Relationship Management System Create Ticket create-ticket.php cross site scripting","id":"CVE-2026-5325"},"packages":[],"prev":{"headline":"priyankark a11y-mcp index.js A11yServer server-side request forgery","id":"CVE-2026-5323"},"products":["Brizy – Page Builder"],"published":"2026-05-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-04","vendors":["themefusecom"]},"summary":"Unauthenticated attackers can inject scripts via form submissions that execute when administrators view the leads page, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-5324/"}