CVE-2026-9199 json
Equalize Digital Accessibility Checker <= 1.42.1 - Missing Authorization to Authenticated (Author+) Arbitrary Accessibility Issue Modification via 'largeBatch' Parameter
published 4mo ago modified 4mo ago also EUVD-2026-37837
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
The Equalize Digital Accessibility Checker – WCAG, ADA, EAA and Section 508 compliance plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.42.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with author-level access and above, to dismiss, ignore, or restore accessibility audit issue records belonging to posts they are not permitted to edit by supplying an issue from their own post as an authorization token to affect matching issues across the entire site. An Author-level user can exploit this by passing largeBatch=true on a dismiss-issue request referencing one of their own post's issues, causing the handler to bulk-modify all site-wide accessibility issues sharing the same 'object' value — including those belonging to administrator-owned posts.
Is CVE-2026-9199 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- equalizedigital Equalize Digital Accessibility Checker – WCAG, ADA, EAA and Section 508 compliance
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/0e5cc0ce-3785-4240-863e-d1396db6e8ef?source=cve
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.42.0/includes/classes/class-rest-api.php#L1247
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.42.0/includes/classes/class-rest-api.php#L1232
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.42.0/includes/classes/class-rest-api.php#L349
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.39.0/includes/classes/class-rest-api.php#L1247
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.39.0/includes/classes/class-rest-api.php#L1232
- plugins.trac.wordpress.org /browser/accessibility-checker/tags/1.39.0/includes/classes/class-rest-api.php#L349
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3553926%40accessibility-checker&new=3553926%40accessibility-che
Sources
- CVE List CVE-2026-9199
- NVD CVE-2026-9199
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.