{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-2897 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-2897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2897 is a low-severity vulnerability in themefusecom Brizy – Page Builder, published on 9 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-2897 and fix it if it is affected.\n\nWhat it is: CVE-2023-2897 is a low-severity vulnerability in themefusecom Brizy – Page Builder, published on 9 Jun 2023. 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-2023-2897 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-2023-2897/ (Markdown: https://insights.sbomify.com/CVE-2023-2897/index.md)","id":"CVE-2023-2897","markdown":"https://insights.sbomify.com/CVE-2023-2897/index.md","name":"CVE-2023-2897","record":{"aliases":["GHSA-5554-v93q-454g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass Maintenance Mode protection by spoofing IP addresses in the X-Forwarded-For header, potentially accessing restricted functionality or sensitive data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"brizy","vendor":"brizy"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"The Brizy Page Builder plugin for WordPress is vulnerable to IP Address Spoofing in versions up to, and including, 2.4.18. This is due to an implicit trust of user-supplied IP addresses in an 'X-Forwarded-For' HTTP header for the purpose of validating allowed IP addresses against a Maintenance Mode whitelist. Supplying a whitelisted IP address within the 'X-Forwarded-For' header allows maintenance mode to be bypassed and may result in the disclosure of potentially sensitive information or allow access to restricted functionality.","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.18 - IP Address Spoofing to Protection Mechanism Bypass","id":"CVE-2023-2897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in Kernel","id":"CVE-2023-2898"},"packages":[],"prev":{"headline":"WP EasyCart \u003c= 5.4.8 - Cross-Site Request Forgery via process_duplicate_product","id":"CVE-2023-2896"},"products":["Brizy – Page Builder"],"published":"2023-06-09","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":"Attackers can bypass Maintenance Mode protection by spoofing IP addresses in the X-Forwarded-For header, potentially accessing restricted functionality or sensitive data.","url":"https://insights.sbomify.com/CVE-2023-2897/"}