CVE-2025-13113
Web Accessibility by accessiBe <= 2.11 - Unauthenticated Sensitive Information Exposure
Description
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.
INFO
Published Date :
Feb. 19, 2026, 3:25 a.m.
Last Modified :
Feb. 19, 2026, 3:25 a.m.
Remotely Exploit :
Yes !
Source :
Wordfence
Affected Products
The following products are affected by CVE-2025-13113
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | MITRE-CVE |
Solution
- Update the Web Accessibility by accessiBe plugin.
- Verify plugin logs do not expose sensitive data.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-13113 vulnerability anywhere in the article.