{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-25012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25012 is a medium-severity missing authorization vulnerability in gfazioli WP Bannerize Pro, published on 3 Feb 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-25012 and fix it if it is affected.\n\nWhat it is: CVE-2026-25012 is a medium-severity missing authorization vulnerability in gfazioli WP Bannerize Pro, published on 3 Feb 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-25012 in the wild and no public exploit code.\n\nAffected product: gfazioli WP Bannerize 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-2026-25012/ (Markdown: https://insights.sbomify.com/CVE-2026-25012/index.md)","id":"CVE-2026-25012","markdown":"https://insights.sbomify.com/CVE-2026-25012/index.md","name":"CVE-2026-25012","record":{"aliases":["GHSA-g35p-qgfm-w6v2"],"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":"Attackers can bypass access controls in WP Bannerize Pro to perform unauthorized actions due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in gfazioli WP Bannerize Pro wp-bannerize-pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Bannerize Pro: from n/a through \u003c= 1.11.0.","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 WP Bannerize Pro plugin \u003c= 1.11.0 - Broken Access Control vulnerability","id":"CVE-2026-25012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Phox Hosting plugin \u003c= 2.0.8 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2026-25013"},"packages":[],"prev":{"headline":"WordPress WP Custom Admin Interface plugin \u003c= 7.41 - Broken Access Control vulnerability","id":"CVE-2026-25011"},"products":["WP Bannerize Pro"],"published":"2026-02-03","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["gfazioli"]},"summary":"Attackers can bypass access controls in WP Bannerize Pro to perform unauthorized actions due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-25012/"}