HomeWordPress vulnerabilitiesWeb Accessibility by accessiBe
Web Accessibility by accessiBe vulnerabilities
Web Accessibility by accessiBe has 2 known vulnerabilities in this database. The most recent published record is dated 19 Feb 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 2.13
- Last updated
- 23 Feb 2026
- Most recent
- 19 Feb 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2025-13113 | Medium 5.3 | Up to 2.11 | Fixed in a later version (latest 2.13) | 19 Feb 2026 |
| Cross-site request forgery (CSRF) CVE-2025-10375 | Medium 4.3 | Up to 2.10 | Fixed in a later version (latest 2.13) | 11 Oct 2025 |
Read the published descriptions
- CVE-2025-13113, 19 Feb 2026
- The Web Accessibility by accessiBe plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.11. This is due to the `accessibe_render_js_in_footer()` function logging the complete plugin options array to the browser console on public pages, without restricting output to privileged users or checking for debug mode. This makes it possible for unauthenticated attackers to view sensitive configuration data, including email addresses, accessiBe user IDs, account IDs, and license information, via the browser console when the widget is disabled. CVE record
- CVE-2025-10375, 11 Oct 2025
- The Web Accessibility By accessiBe plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.10. This is due to missing nonce validation on multiple AJAX actions including accessibe_signup, accessibe_login, accessibe_license_trial, accessibe_modify_config, and accessibe_add_verification_page. This makes it possible for unauthenticated attackers to modify plugin settings and create verification files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run Web Accessibility by accessiBe
If you run Web Accessibility by accessiBe, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Web Accessibility by accessiBe vulnerabilities
Free. We email you when a new vulnerability is published for Web Accessibility by accessiBe, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.