CVE-2025-14980

BetterDocs <= 4.3.3 - Authenticated (Contributor+) Sensitive Information Exposure

2026-01-08 17:52
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 4.3.4
Affected Version
<= 4.3.3
CVSS
6.5Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-14980
View all BetterDocs – AI Documentation, Knowledge Base, MCP Server, Docs, Wikis, FAQ & Chatbot vulnerabilities

At a glance

CVE-2025-14980 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the BetterDocs WordPress plugin, affecting versions <= 4.3.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.3.4; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The BetterDocs plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.3.3 via the scripts() function. This makes it possible for authenticated attackers, with contributor-level access and above, to extract sensitive data including the OpenAI API key stored in plugin settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

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

BetterDocs <= 4.3.3 carries this weakness at scripts(), and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For BetterDocs the fix is 4.3.4: builds <= 4.3.3 are affected, anything from 4.3.4 onward is not.

Remediation

Update to version 4.3.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: BetterDocs 4.3.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C