BetterDocs <= 4.3.11 - Missing Authorization to Authenticated (Subscriber+) Unauthorized AI API Usage
Strategic Overview
- Status
- Patched in 4.3.12
- Affected Version
<= 4.3.11- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-6393
At a glance
CVE-2026-6393 is a medium-severity Missing Authorization vulnerability in the BetterDocs WordPress plugin, affecting versions <= 4.3.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.3.12; sites on affected versions should update now. Disclosed April 2026, reported by h0xilo.
Vulnerability Overview
The BetterDocs plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 4.3.11. This is due to a missing capability check in the generate_openai_content_callback() function, which relies solely on a nonce rather than verifying user permissions. This makes it possible for authenticated attackers, with subscriber-level access and above, to trigger OpenAI API calls using the site's configured API key with arbitrary user-controlled prompts, leading to unauthorized consumption of the site owner's paid AI API quota.
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.
CWE-862: Missing Authorization
BetterDocs <= 4.3.11 carries this weakness at generate_openai_content_callback(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For BetterDocs the fix is 4.3.12: builds <= 4.3.11 are affected, anything from 4.3.12 onward is not.
Remediation
Update to version 4.3.12, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: BetterDocs 4.3.12 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in BetterDocs – AI Documentation, Knowledge Base, Docs, Wikis, FAQ with Chatbot
- 9.8CVE-2024-30226: BetterDocs PHP Object Injection
CVE-2024-30226 - 8.8CVE-2024-43129: BetterDocs <= 3.5.8 Local File Inclusion
CVE-2024-43129 - 7.2CVE-2026-11371: BetterDocs <= 4.5.4 Stored Cross-Site Scripting
CVE-2026-11371 - 6.5CVE-2026-15104: BetterDocs <= 4.6.0 SQL Injection
CVE-2026-15104 - 6.5CVE-2025-14980: BetterDocs <= 4.3.3 Sensitive Information Exposure
CVE-2025-14980 - 6.4CVE-2026-65562: BetterDocs Stored XSS
CVE-2026-65562 - 6.4CVE-2026-12157: BetterDocs <= 4.5.3 Stored Cross-Site Scripting
CVE-2026-12157 - 6.4CVE-2026-3875: BetterDocs <= 4.3.8 Stored Cross-Site Scripting
CVE-2026-3875
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C