{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-26902 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26902 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26902 is a medium-severity vulnerability in Brizy Pro, published on 9 Apr 2025. 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-2025-26902 and fix it if it is affected.\n\nWhat it is: CVE-2025-26902 is a medium-severity vulnerability in Brizy Pro, published on 9 Apr 2025. 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-2025-26902 in the wild and no public exploit code.\n\nAffected product: Brizy Pro. 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-2025-26902/ (Markdown: https://insights.sbomify.com/CVE-2025-26902/index.md)","id":"CVE-2025-26902","markdown":"https://insights.sbomify.com/CVE-2025-26902/index.md","name":"CVE-2025-26902","record":{"aliases":["GHSA-4mf7-rwpr-69qr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can trick authenticated users into performing unwanted actions in the Brizy Pro WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"brizy","vendor":"brizy"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Brizy Brizy Pro allows Cross Site Request Forgery.This issue affects Brizy Pro: from n/a through 2.6.1.","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":"WordPress Brizy Pro plugin \u003c= 2.6.1 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2025-26902","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress InPost Gallery plugin \u003c= 2.1.4.3 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2025-26903"},"packages":[],"prev":{"headline":"WordPress Brizy Pro plugin \u003c= 2.6.1 - Broken Access Control vulnerability","id":"CVE-2025-26901"},"products":["Brizy Pro"],"published":"2025-04-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-28","vendors":["Brizy"]},"summary":"An attacker can trick authenticated users into performing unwanted actions in the Brizy Pro WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-26902/"}