Web Accessibility by accessiBe at a glance
- 5 publicly disclosed vulnerabilities. The most recent was disclosed on Feb 18, 2026.
- Ranked #1724 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 2.13 (released Feb 23, 2026). The most recent security fix shipped in 2.12.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Web Accessibility by accessiBe version
Enter the Web Accessibility by accessiBe version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Web Accessibility by accessiBe”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Web Accessibility by accessiBe”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.13). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Web Accessibility by accessiBe vulnerabilities
Web Accessibility by accessiBe <= 2.11 - Unauthenticated Sensitive Information Exposure
Information disclosure · CVE-2025-13113
Affected versions: ≤ 2.11
Fixed in: 2.12
Severity: Medium 5.3 · Disclosed Feb 18, 2026
Web Accessibility By accessiBe <= 2.10 - Missing Authorization
Missing authorization · CVE-2025-49920
Affected versions: ≤ 2.10
Fixed in: 2.11
Severity: Medium 4.3 · Disclosed Oct 27, 2025
Web Accessibility By accessiBe <= 2.10 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2025-10375
Affected versions: ≤ 2.10
Fixed in: 2.11
Severity: Medium 4.3 · Disclosed Oct 10, 2025
Web Accessibility By accessiBe <= 2.5 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-26981
Affected versions: ≤ 2.5
Fixed in: 2.6
Severity: Medium 6.1 · Disclosed Feb 23, 2025
Web Accessibility By accessiBe <= 1.15 - Authenticated (Administrator+) Stored Cross-Site Scripting
Cross-site scripting (XSS)
Affected versions: ≤ 1.15
Fixed in: 1.16
Severity: Medium 4.4 · Disclosed Jul 27, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Web Accessibility by accessiBe <= 2.11 - Unauthenticated Sensitive Information ExposureInformation disclosure · CVE-2025-13113 | ≤ 2.11 | 2.12 | Medium 5.3 | Feb 18, 2026 |
| Web Accessibility By accessiBe <= 2.10 - Missing AuthorizationMissing authorization · CVE-2025-49920 | ≤ 2.10 | 2.11 | Medium 4.3 | Oct 27, 2025 |
| Web Accessibility By accessiBe <= 2.10 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2025-10375 | ≤ 2.10 | 2.11 | Medium 4.3 | Oct 10, 2025 |
| Web Accessibility By accessiBe <= 2.5 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-26981 | ≤ 2.5 | 2.6 | Medium 6.1 | Feb 23, 2025 |
| Web Accessibility By accessiBe <= 1.15 - Authenticated (Administrator+) Stored Cross-Site ScriptingCross-site scripting (XSS) | ≤ 1.15 | 1.16 | Medium 4.4 | Jul 27, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Feb 18, 2026.
Most common weaknesses in Web Accessibility by accessiBe
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Missing authorization
1 issue
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Frequently asked questions
Is Web Accessibility by accessiBe safe to use?
Web Accessibility by accessiBe is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.13) and turn on automatic updates.
How do I find which version of Web Accessibility by accessiBe my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesWeb Accessibility by accessiBe on WordPress.org