{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4443 exists.","fix":"No fix has been published for CVE-2022-4443 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4443 is a medium-severity vulnerability in Unknown BruteBank, published on 23 Jan 2023. 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-2022-4443 and fix it if it is affected.\n\nWhat it is: CVE-2022-4443 is a medium-severity vulnerability in Unknown BruteBank, published on 23 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4443 exists.\n\nAffected product: Unknown BruteBank. 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-2022-4443/ (Markdown: https://insights.sbomify.com/CVE-2022-4443/index.md)","id":"CVE-2022-4443","markdown":"https://insights.sbomify.com/CVE-2022-4443/index.md","name":"CVE-2022-4443","record":{"aliases":["GHSA-hgrr-97rg-c34m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can force logged-in admins to change BruteBank plugin settings via CSRF, potentially weakening security configurations.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"brutebank","vendor":"brutebank"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"The BruteBank WordPress plugin before 1.9 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"BruteBank - WP Security \u0026 Firewall \u003c 1.9 - Settings Update via CSRF","id":"CVE-2022-4443","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"ipti br.tag cross site scripting","id":"CVE-2022-4444"},"packages":[],"prev":{"headline":"WCK \u003c 2.3.3 - Admin+ Stored XSS","id":"CVE-2022-4442"},"products":["BruteBank"],"published":"2023-01-23","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-02","vendors":["Unknown"]},"summary":"Attackers can force logged-in admins to change BruteBank plugin settings via CSRF, potentially weakening security configurations.","url":"https://insights.sbomify.com/CVE-2022-4443/"}