CVE-2026-14481 MEDIUM

CVE-2026-14481: Equalize Digital Accessibility Checker <= 1.46.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'html' Parameter

Vendor Equalizedigital
Product Equalize Digital Accessibility Checker – WCAG, ADA, EAA and Section 508 compliance
Weakness CWE-79 · XSS
Published July 23, 2026
Last update July 23, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Equalize Digital Accessibility Checker – WCAG, ADA, EAA and Section 508 compliance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'html' parameter in all versions up to, and including, 1.46.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to have the ability to edit a post, as the REST endpoint /accessibility-checker/v1/post-scan-results/{id} is guarded only by the edit_post capability on the target post.

Explanation of Vulnerability in Simple Terms

02Summary

The Equalize Digital Accessibility Checker plugin contains a cross-site scripting (XSS) vulnerability in versions up to 1.46.0. An authenticated user with low privileges can inject malicious scripts that execute in other users' browsers, potentially stealing session data or performing actions on their behalf. The vulnerability affects the plugin's scope across the site.

What an attacker can do

03Attacker Capabilities

Inject and execute malicious JavaScript in other users' browsers to steal data or perform unauthorized actions.

Potential impact on your site

04Site Impact

Authenticated users' sessions and data are at risk; attackers can impersonate users and modify site content or settings.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account (e.g., subscriber or contributor role) on the WordPress site.

Key dates

06Disclosure timeline

July 23, 2026 CVE published

Related vulnerabilities

08Related CVE