WordPress plugin
Accessibly – WordPress Website Accessibility security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High1
- Medium0
- Low0
All Accessibly – WordPress Website Accessibility vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Missing Authorization to Unauthenticated Stored Cross-Site Scripting via Widget Source Injection via REST API ≤3.0.3No patch available | CVE-2026-3643 |
- High7.2Missing Authorization to Unauthenticated Stored Cross-Site Scripting via Widget Source Injection via REST API
≤3.0.3No patch available
Accessibly – WordPress Website Accessibility: common questions
Does Accessibly – WordPress Website Accessibility have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Accessibly – WordPress Website Accessibility: 1 high. At least one is not fixed in the latest version.
How do I check which version of Accessibly – WordPress Website Accessibility I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Accessibly – WordPress Website Accessibility vulnerability?
CVE-2026-3643, published Apr 14, 2026: Accessibly <= 3.0.3 - Missing Authorization to Unauthenticated Stored Cross-Site Scripting via Widget Source Injection via REST API. Severity: High (CVSS 7.2).
Is any Accessibly – WordPress Website Accessibility vulnerability listed in CISA KEV?
No. None of the known Accessibly – WordPress Website Accessibility vulnerabilities is currently listed in the CISA KEV catalog.
