WP Accessibility Helper <= 0.6.2.8 - Missing Authorization to Authenticated (Subscriber+) Limited Settings Update
Strategic Overview
- Status
- Patched in 0.6.2.9
- Affected Plugin
- WP Accessibility Helper (WAH)
- Affected Version
<= 0.6.2.8- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-5987
At a glance
CVE-2024-5987 is a medium-severity Missing Authorization vulnerability in the WP Accessibility Helper (WAH) WordPress plugin, affecting versions <= 0.6.2.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.6.2.9; sites on affected versions should update now. Disclosed August 2024, reported by Lucio Sá.
Vulnerability Overview
The WP Accessibility Helper (WAH) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_contrast_variations' and 'save_empty_contrast_variations' functions in all versions up to, and including, 0.6.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to edit or delete contrast settings. Please note these issues were patched in 0.6.2.8, though it broke functionality and the vendor has not responded to our follow-ups.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Accessibility Helper (WAH) <= 0.6.2.8 carries this weakness at save_contrast_variations, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Accessibility Helper (WAH) the fix is 0.6.2.9: builds <= 0.6.2.8 are affected, anything from 0.6.2.9 onward is not.
Remediation
Update to version 0.6.2.9, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Accessibility Helper (WAH) 0.6.2.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Accessibility Helper (WAH)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C