{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4260 exists.","fix":"No fix has been published for CVE-2022-4260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4260 is a medium-severity cross-site scripting vulnerability in Unknown WP-Ban, published on 2 Jan 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-4260 and fix it if it is affected.\n\nWhat it is: CVE-2022-4260 is a medium-severity cross-site scripting vulnerability in Unknown WP-Ban, published on 2 Jan 2023. An attacker needs administrator access to exploit it, 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-4260 exists.\n\nAffected product: Unknown WP-Ban. 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-4260/ (Markdown: https://insights.sbomify.com/CVE-2022-4260/index.md)","id":"CVE-2022-4260","markdown":"https://insights.sbomify.com/CVE-2022-4260/index.md","name":"CVE-2022-4260","record":{"aliases":["GHSA-7wx2-wjvp-v5h2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Admin users can inject malicious scripts via unsanitized settings in the WP-Ban plugin, leading to stored XSS attacks.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp-ban","vendor":"wp-ban_project"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-4260.yaml","stars":null,"title":"WordPress WP-Ban \u003c1.69.1 - Stored Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"WP-Ban \u003c 1.69.1 - Admin+ Stored XSS","id":"CVE-2022-4260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Rapid7 Nexpose Update Validation Issue","id":"CVE-2022-4261"},"packages":[],"prev":{"headline":"Authenticated SQL Injection on Alerts in Guardian/CMC before 22.5.2","id":"CVE-2022-4259"},"products":["WP-Ban"],"published":"2023-01-02","related":[{"cvss_score":4.3,"headline":"Security feature bypass in n/a","id":"CVE-2014-6230","kev_date_added":null,"published":"2014-10-25"},{"cvss_score":3.5,"headline":"WP-Ban ban-options.php cross site scripting","id":"CVE-2022-4631","kev_date_added":null,"published":"2022-12-21"},{"cvss_score":3.5,"headline":"WP-Ban ban-options.php toggle_checkbox cross site scripting","id":"CVE-2021-4252","kev_date_added":null,"published":"2022-12-18"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["Unknown"]},"summary":"Admin users can inject malicious scripts via unsanitized settings in the WP-Ban plugin, leading to stored XSS attacks.","url":"https://insights.sbomify.com/CVE-2022-4260/"}