WP Accessibility Helper (WAH)
wp-accessibility-helper · plugin
Known security vulnerabilities for WP Accessibility Helper (WAH). Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
2 exploitable without logging in · latest Jul 23, 2026
Listed on wordpress.org · latest 0.6.7 · last updated Sep 2, 2026 · 10K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2024-31423login required≤ 0.6.2.5
WordPress WP Accessibility Helper (WAH) plugin <= 0.6.2.5 - Broken Access Control vulnerability
- Medium 5.3
CVE-2024-37926unauthenticated≤ 0.6.2.9
WordPress WP Accessibility Helper (WAH) plugin <= 0.6.2.9 - Broken Access Control vulnerability
- Medium 4.3
CVE-2026-24537unauthenticated · needs a click≤ 0.6.6
WordPress WP Accessibility Helper (WAH) plugin <= 0.6.6 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2023-41869login required≤ 0.6.2.4
WordPress WP Accessibility Helper (WAH) plugin <= 0.6.2.4 - Broken Access Control vulnerability
- Medium 4.3
CVE-2024-5987subscriber+≤ 0.6.2.8
WP Accessibility Helper <= 0.6.2.8 - Missing Authorization to Authenticated (Subscriber+) Limited Settings Update
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).