WP Accessibility Helper (WAH) at a glance
- 6 publicly disclosed vulnerabilities. The most recent was disclosed on Jul 22, 2026.
- Ranked #1714 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 0.6.7 (released Sep 2, 2026). The most recent security fix shipped in 0.6.7.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your WP Accessibility Helper (WAH) version
Enter the WP Accessibility Helper (WAH) version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “WP Accessibility Helper (WAH)”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WP Accessibility Helper (WAH)”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (0.6.7). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known WP Accessibility Helper (WAH) vulnerabilities
WP Accessibility Helper (WAH) <= 0.6.6 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2026-24537
Affected versions: ≤ 0.6.6
Fixed in: 0.6.7
Severity: Medium 4.3 · Disclosed Jul 22, 2026
WP Accessibility Helper <= 0.6.2.8 - Missing Authorization to Authenticated (Subscriber+) Limited Settings Update
Missing authorization · CVE-2024-5987
Affected versions: ≤ 0.6.2.8
Fixed in: 0.6.2.9
Severity: Medium 5.4 · Disclosed Aug 28, 2024
WP Accessibility Helper (WAH) <= 0.6.2.9 - Missing Authorization
Missing authorization · CVE-2024-37926
Affected versions: ≤ 0.6.2.9
Fixed in: 0.6.3
Severity: Medium 5.3 · Disclosed Jul 9, 2024
WP Accessibility Helper (WAH) <= 0.6.2.5 - Missing Authorization
Missing authorization · CVE-2024-31423
Affected versions: ≤ 0.6.2.5
Fixed in: 0.6.2.6
Severity: Medium 4.3 · Disclosed Apr 10, 2024
WP Accessibility Helper (WAH) <= 0.6.2.4 - Missing Authorization via AJAX action
Missing authorization · CVE-2023-41869
Affected versions: ≤ 0.6.2.4
Fixed in: 0.6.2.5
Severity: Medium 4.3 · Disclosed Sep 5, 2023
WP Accessibility Helper <= 0.6.0.6 - Reflected Cross-Site Scripting via wahi
Cross-site scripting (XSS) · CVE-2022-0150
Affected versions: < 0.6.0.7
Fixed in: 0.6.0.7
Severity: Medium 6.1 · Disclosed Jun 20, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WP Accessibility Helper (WAH) <= 0.6.6 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2026-24537 | ≤ 0.6.6 | 0.6.7 | Medium 4.3 | Jul 22, 2026 |
| WP Accessibility Helper <= 0.6.2.8 - Missing Authorization to Authenticated (Subscriber+) Limited Settings UpdateMissing authorization · CVE-2024-5987 | ≤ 0.6.2.8 | 0.6.2.9 | Medium 5.4 | Aug 28, 2024 |
| WP Accessibility Helper (WAH) <= 0.6.2.9 - Missing AuthorizationMissing authorization · CVE-2024-37926 | ≤ 0.6.2.9 | 0.6.3 | Medium 5.3 | Jul 9, 2024 |
| WP Accessibility Helper (WAH) <= 0.6.2.5 - Missing AuthorizationMissing authorization · CVE-2024-31423 | ≤ 0.6.2.5 | 0.6.2.6 | Medium 4.3 | Apr 10, 2024 |
| WP Accessibility Helper (WAH) <= 0.6.2.4 - Missing Authorization via AJAX actionMissing authorization · CVE-2023-41869 | ≤ 0.6.2.4 | 0.6.2.5 | Medium 4.3 | Sep 5, 2023 |
| WP Accessibility Helper <= 0.6.0.6 - Reflected Cross-Site Scripting via wahiCross-site scripting (XSS) · CVE-2022-0150 | < 0.6.0.7 | 0.6.0.7 | Medium 6.1 | Jun 20, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 22, 2026.
Most common weaknesses in WP Accessibility Helper (WAH)
Missing authorization
4 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site request forgery (CSRF)
1 issue
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Cross-site scripting (XSS)
1 issue
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Frequently asked questions
Is WP Accessibility Helper (WAH) safe to use?
WP Accessibility Helper (WAH) is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (0.6.7) and turn on automatic updates.
How do I find which version of WP Accessibility Helper (WAH) my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesWP Accessibility Helper (WAH) on WordPress.org