{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0150 exists.","fix":"No fix has been published for CVE-2022-0150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0150 is a medium-severity cross-site scripting vulnerability in Unknown WP Accessibility Helper (WAH), published on 28 Feb 2022. 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-0150 and fix it if it is affected.\n\nWhat it is: CVE-2022-0150 is a medium-severity cross-site scripting vulnerability in Unknown WP Accessibility Helper (WAH), published on 28 Feb 2022. 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-0150 exists.\n\nAffected product: Unknown WP Accessibility Helper (WAH). 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-0150/ (Markdown: https://insights.sbomify.com/CVE-2022-0150/index.md)","id":"CVE-2022-0150","markdown":"https://insights.sbomify.com/CVE-2022-0150/index.md","name":"CVE-2022-0150","record":{"aliases":["GHSA-47jf-42qg-82r8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via the wahi parameter in WP Accessibility Helper, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_accessibility_helper","vendor":"wp_accessibility_helper_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WP Accessibility Helper (WAH) WordPress plugin before 0.6.0.7 does not sanitise and escape the wahi parameter before outputting back its base64 decode value in the page, leading to a Reflected Cross-Site Scripting issue","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-0150.yaml","stars":null,"title":"WordPress Accessibility Helper \u003c0.6.0.7 - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"WP Accessibility Helper (WAH) \u003c 0.6.0.7 - Reflected Cross-Site Scripting (XSS)","id":"CVE-2022-0150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in GitLab","id":"CVE-2022-0151"},"packages":[],"prev":{"headline":"WooCommerce – Store Exporter \u003c 2.7.1 - Reflected Cross-Site Scripting (XSS)","id":"CVE-2022-0149"},"products":["WP Accessibility Helper (WAH)"],"published":"2022-02-28","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts via the wahi parameter in WP Accessibility Helper, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2022-0150/"}