# CVE-2025-13113: Web Accessibility by accessiBe <= 2.11 - Unauthenticated Sensitive Information Exposure

> Unauthenticated attackers can view sensitive configuration data, including emails and license keys, via the browser console in the Web Accessibility by accessiBe plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6rq3-qg6r-q3cx

## What is CVE-2025-13113?

CVE-2025-13113 is a medium-severity vulnerability in accessibewp Web Accessibility by accessiBe, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-13113?


## How do I fix CVE-2025-13113?

No fix has been published for CVE-2025-13113 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13113 being exploited?

There is no known exploitation of CVE-2025-13113 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13113 and fix it if it is affected.

What it is: CVE-2025-13113 is a medium-severity vulnerability in accessibewp Web Accessibility by accessiBe, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13113 in the wild and no public exploit code.

Affected product: accessibewp Web Accessibility by accessiBe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13113/ (Markdown: https://insights.sbomify.com/CVE-2025-13113/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13113
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13113
- OSV: https://osv.dev/vulnerability/CVE-2025-13113

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13113/
Summaries are generated and may contain mistakes; the official description above is the record.