{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3409 is a medium-severity vulnerability in Bricks, published on 17 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-3409 and fix it if it is affected.\n\nWhat it is: CVE-2023-3409 is a medium-severity vulnerability in Bricks, published on 17 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-3409 in the wild and no public exploit code.\n\nAffected product: Bricks. 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-2023-3409/ (Markdown: https://insights.sbomify.com/CVE-2023-3409/index.md)","id":"CVE-2023-3409","markdown":"https://insights.sbomify.com/CVE-2023-3409/index.md","name":"CVE-2023-3409","record":{"aliases":["GHSA-9jvc-fg8h-cfgg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress theme","requires_auth":"none","summary":"Attackers can trick administrators into resetting Bricks theme settings via forged requests, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"bricks","vendor":"bricksbuilder"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Bricks theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.1. This is due to missing or incorrect nonce validation on the 'reset_settings' function. This makes it possible for unauthenticated attackers to reset the theme's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Bricks \u003c= 1.8.1 - Cross-Site Request Forgery via reset_settings","id":"CVE-2023-3409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Bricks \u003c= 1.10.1 - Authenticated (Bricks Page Builder Access+) Stored Cross-Site Scripting","id":"CVE-2023-3410"},"packages":[],"prev":{"headline":"Bricks \u003c= 1.8.1 - Cross-Site Request Forgery via save_settings","id":"CVE-2023-3408"},"products":["Bricks"],"published":"2024-08-17","related":[{"cvss_score":8.8,"headline":"Code injection in Bricks","id":"CVE-2022-3401","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":7.1,"headline":"Bricksbuilder \u003c= 1.9.6.1 - Authenticated (Contributor+) Privilege Escalation via create_autosave","id":"CVE-2024-2297","kev_date_added":null,"published":"2025-02-27"},{"cvss_score":6.5,"headline":"Missing authorization in Bricks","id":"CVE-2022-3400","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":5.4,"headline":"Bricks \u003c= 1.10.1 - Authenticated (Bricks Page Builder Access+) Stored Cross-Site Scripting","id":"CVE-2023-3410","kev_date_added":null,"published":"2024-09-14"},{"cvss_score":4.3,"headline":"Bricks \u003c= 1.8.1 - Cross-Site Request Forgery via save_settings","id":"CVE-2023-3408","kev_date_added":null,"published":"2024-08-17"},{"cvss_score":4.3,"headline":"Bricks Builder \u003c= 1.9.8 - Insecure Direct Object Reference","id":"CVE-2024-4874","kev_date_added":null,"published":"2024-06-22"}],"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":["Bricks Builder"]},"summary":"Attackers can trick administrators into resetting Bricks theme settings via forged requests, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2023-3409/"}