EUVD-2026-47921
GHSA-jx87-9h27-35h7
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Stored XSS requires a victim to visit the injected page (UI:R per CVSS 3.1 spec); contributor edit_post rights give PR:L; no server-side availability impact exists.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Stored Cross-Site Scripting in the Equalize Digital Accessibility Checker WordPress plugin (all versions through 1.46.0) permits authenticated contributors to inject persistent malicious scripts via the 'html' parameter of the plugin's REST API endpoint, which executes in the browser of any subsequent visitor to the affected post. The attack surface is the unguarded /accessibility-checker/v1/post-scan-results/{id} endpoint, protected only by the low-privilege edit_post WordPress capability, making exploitation trivial for any contributor-level account on multi-author sites. No public exploit has been identified and the plugin is absent from CISA KEV, but the low authentication bar and persistent payload nature elevate real-world risk beyond the medium CVSS score suggests for sites with multiple editors.
Technical ContextAI
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically the failure to sanitize input on ingestion and escape output on rendering for the 'html' parameter accepted by the REST endpoint /accessibility-checker/v1/post-scan-results/{id}. Source code inspection via the WordPress plugin trac repository across versions 1.44.1 and 1.45.0 confirms the vulnerable code paths spread across admin/class-ajax.php (L529), includes/helper-functions.php (L759), includes/classes/class-rest-api.php (L520), and admin/class-insert-rule-data.php (L68). The endpoint's only access control is a check for the WordPress edit_post capability on the target post, a permission held by contributors and above - a deliberately broad set in any collaborative publishing environment. The CVSS S:C (scope changed) metric reflects that the injected payload crosses the server-side plugin boundary into the victim's browser execution context. Affected product per CPE: cpe:2.3:a:equalizedigital:equalize_digital_accessibility_checker_-_wcag,_ada,_eaa_and_section_508_compliance:*:*:*:*:*:*:*:*.
RemediationAI
Update the Equalize Digital Accessibility Checker plugin to the version released after 1.46.0 as soon as it is available in the WordPress plugin repository. An upstream fix has been committed per the SVN changeset at plugins.trac.wordpress.org/changeset?reponame=&old=3608913%40accessibility-checker&new=3608913%40accessibility-checker; however, the exact patched release version number is not confirmed in the available input data and must be verified directly in the WordPress plugin directory before upgrading. As an interim compensating control, administrators should audit and reduce contributor-level accounts to only trusted users, since any contributor with edit_post rights on a post can exploit this flaw - reducing contributor account sprawl directly shrinks the attack surface without disrupting site functionality. A secondary option is to use a WAF or security plugin (e.g., Wordfence, Cloudflare WAF) to block or rate-limit POST requests to the /accessibility-checker/v1/post-scan-results/ REST route, though this will disable scan result submission functionality and may impair the plugin's core operation. Disabling the plugin entirely eliminates the vulnerability surface but also removes accessibility compliance reporting.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today