Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13921: CWE-862 Missing Authorization in wedevs weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot

0
Medium
VulnerabilityCVE-2025-13921cvecve-2025-13921cwe-862
Published: Fri Jan 23 2026 (01/23/2026, 13:24:24 UTC)
Source: CVE Database V5
Vendor/Project: wedevs
Product: weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot

Description

CVE-2025-13921 is a medium severity vulnerability in the weDocs WordPress plugin that allows authenticated users with Subscriber-level access or higher to modify any documentation post due to missing authorization checks. The flaw exists in the 'wedocs_user_documentation_handling_capabilities' function and affects all versions up to 2. 1. 16, with a partial patch applied in that version. Exploitation requires no user interaction beyond authentication and can lead to unauthorized modification or loss of documentation data. The vulnerability does not impact confidentiality or availability but compromises data integrity within the plugin. No known exploits are currently reported in the wild. European organizations using this plugin in their WordPress environments should prioritize updating and reviewing user permissions to mitigate risk. Countries with high WordPress adoption and active use of knowledge base plugins are more likely to be affected. The CVSS score is 4.

AI-Powered Analysis

AILast updated: 01/23/2026, 14:05:17 UTC

Technical Analysis

CVE-2025-13921 is a vulnerability classified under CWE-862 (Missing Authorization) found in the weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress. The issue arises from the absence of proper capability checks within the 'wedocs_user_documentation_handling_capabilities' function, which governs user permissions for editing documentation posts. This flaw allows any authenticated user with at least Subscriber-level privileges to bypass intended restrictions and edit any documentation content, potentially leading to unauthorized modifications or data loss. The vulnerability affects all versions up to and including 2.1.16, where a partial patch was introduced but did not fully remediate the issue. The attack vector is remote over the network, requiring only low complexity and no user interaction beyond authentication. The impact is limited to integrity, as confidentiality and availability are not affected. No known exploits have been reported in the wild, but the vulnerability poses a risk to organizations relying on the plugin for maintaining accurate and trustworthy documentation. The CVSS v3.1 base score is 4.3, reflecting a medium severity due to the need for authenticated access and limited impact scope.

Potential Impact

For European organizations, this vulnerability can undermine the integrity of internal or public-facing documentation managed via the weDocs plugin. Unauthorized edits could lead to misinformation, operational disruptions, or reputational damage if critical knowledge base content is altered maliciously. Organizations relying on these documents for compliance, customer support, or internal processes may face increased risk of errors or miscommunication. While the vulnerability does not directly compromise sensitive data confidentiality or system availability, the potential for data tampering can indirectly affect business operations and trustworthiness. The risk is heightened in environments where multiple users have Subscriber or higher access levels without strict role management. Given the widespread use of WordPress in Europe and the popularity of documentation plugins, the threat is relevant especially for sectors with high dependency on accurate documentation such as technology firms, educational institutions, and government agencies.

Mitigation Recommendations

1. Immediately update the weDocs plugin to the latest version beyond 2.1.16 once a complete patch is released, as the current partial fix does not fully resolve the issue. 2. Review and tighten WordPress user role assignments to ensure that only trusted users have Subscriber-level or higher access, minimizing the attack surface. 3. Implement additional access control mechanisms such as custom capability checks or role-based access control plugins to enforce stricter editing permissions on documentation posts. 4. Monitor and audit changes to documentation content regularly to detect unauthorized modifications promptly. 5. Consider isolating critical documentation environments or using alternative plugins with robust authorization controls if timely patching is not feasible. 6. Educate administrators and users about the risks of privilege misuse and enforce strong authentication policies to reduce the chance of compromised accounts being exploited.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-02T19:00:31.637Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69737cc14623b1157c442f09

Added to database: 1/23/2026, 1:50:57 PM

Last enriched: 1/23/2026, 2:05:17 PM

Last updated: 1/23/2026, 4:14:38 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats