weDocs <= 2.1.16 - Missing Authorization to Authenticated (Subscriber+) Documentation Post Update
Strategic Overview
- Status
- Patched in 2.1.17
- Affected Version
<= 2.1.16- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-13921
At a glance
CVE-2025-13921 is a medium-severity Missing Authorization vulnerability in the weDocs WordPress plugin, affecting versions <= 2.1.16. 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 2.1.17; sites on affected versions should update now. Disclosed January 2026, reported by blue0x1.
Vulnerability Overview
The weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress is vulnerable to unauthorized modification or loss of data due to a missing capability check on the 'wedocs_user_documentation_handling_capabilities' function in all versions up to, and including, 2.1.16. This makes it possible for authenticated attackers, with Subscriber-level access and above, to edit any documentation post. The vulnerability was partially patched in version 2.1.16.
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
weDocs <= 2.1.16 carries this weakness at wedocs_user_documentation_handling_capabilities, 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 weDocs the fix is 2.1.17: builds <= 2.1.16 are affected, anything from 2.1.17 onward is not.
Remediation
Update to version 2.1.17, 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: weDocs 2.1.17 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 weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C