dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-13113

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The accessiBe WordPress plugin versions up to 2.11 exposes sensitive configuration data through the browser console on public pages. The accessibe_render_js_in_footer() function outputs the complete plugin options array without checking user privileges or debug mode settings, leaking email addresses, user IDs, account IDs, and license information to unauthenticated visitors.

MitigationUpdate the accessiBe plugin to version 2.12 or later. Until then, consider disabling the widget and reviewing whether the plugin is necessary, as the vulnerability is exploitable by any visitor viewing the browser console.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm accessiBe plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'accessiBe' in the list
    Affected if accessiBe plugin appears in the installed plugins list
  2. Check installed version number
    In the Plugins list, locate the version number displayed beneath the accessiBe plugin name, or check the plugin's main file header for the Version constant
    Affected if version is 2.11 or earlier
  3. Verify plugin is active on public pages
    Visit any public-facing page on the WordPress site and view the page source or check if the accessiBe widget loads
    Affected if the plugin is active and rendering content on public pages
  4. Inspect browser console for exposed data
    Open a public page in a browser, right-click, select Inspect, go to the Console tab, and search for strings like 'email', 'user', 'account', 'license', or 'key' in the console output
    Affected if sensitive information such as email addresses, user IDs, account IDs, or license keys appears in the console without authentication

If the accessiBe plugin version is 2.11 or earlier and is active on the site, the sensitive configuration data is being exposed to all visitors through the browser console.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the accessiBe plugin to version 2.12 or later. Until then, consider disabling the widget and reviewing whether the plugin is necessary, as the vulnerability is exploitable by any visitor viewing the browser console.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13113 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data