Description

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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.4",
  "pubDate": "2026-07-23T10:16:49.787Z",
  "pubdate": "2026-07-23T10:16:49.787Z",
  "executiveSummary": "A Stored Cross-Site Scripting (XSS) vulnerability exists in the Equalize Digital Accessibility Checker – WCAG, ADA, EAA and Section 508 compliance plugin for WordPress in all versions up to, and including, 1.46.0.\nThe flaw allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts into pages.\nThe injected scripts execute whenever a user accesses the affected page, leading to potential session hijacking, defacement, or administrative action redirection.\nThe vulnerability stems from insufficient input sanitization and output escaping on the 'html' parameter.\nExploitation requires the attacker to possess the capability to edit a post and target the unprotected or inadequately guarded REST endpoint /accessibility-checker/v1/post-scan-results/{id}.\nThe risk is heightened because the endpoint relies solely on the edit_post capability on the specific target post.",
  "technicalDetails": "The vulnerability resides in the Equalize Digital Accessibility Checker plugin for WordPress, specifically affecting all versions up to, and including, 1.46.0.\nThe root cause of the vulnerability is the lack of proper input sanitization and output escaping applied to the 'html' parameter processed by the application.\nThe vulnerable component is the REST API endpoint located at /accessibility-checker/v1/post-scan-results/{id}.\nAccess control to this endpoint is insufficiently restricted, as it is guarded only by the edit_post capability on the target post.\nAn authenticated attacker holding a contributor-level role or higher possesses the necessary privileges to edit posts and interact with this endpoint.\nThe attack flow proceeds as follows: First, the authenticated attacker crafts a malicious payload containing arbitrary web scripts embedded within the 'html' parameter. Second, the attacker submits this payload to the vulnerable REST endpoint /accessibility-checker/v1/post-scan-results/{id} for a post they are able to edit. Third, because the input is insufficiently sanitized, the malicious script is stored persistently within the database or application state associated with the post scan results. Finally, when any user—including higher-privileged administrators—accesses the injected page, the stored script executes within the context of their browser session.\nThe impact of successful exploitation includes arbitrary script execution in the context of other users' sessions, enabling potential actions such as session token theft, credential harvesting, or unauthorized modifications to the WordPress site depending on the privileges of the victim viewing the page."
}