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-2026-30857: CWE-639: Authorization Bypass Through User-Controlled Key in Tencent WeKnora

0
Medium
VulnerabilityCVE-2026-30857cvecve-2026-30857cwe-639
Published: Sat Mar 07 2026 (03/07/2026, 16:33:45 UTC)
Source: CVE Database V5
Vendor/Project: Tencent
Product: WeKnora

Description

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.0, a cross-tenant authorization bypass in the knowledge base copy endpoint allows any authenticated user to clone (duplicate) another tenant’s knowledge base into their own tenant by knowing/guessing the source knowledge base ID. This enables bulk data exfiltration (document/FAQ content) across tenants. This issue has been patched in version 0.3.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/14/2026, 20:00:46 UTC

Technical Analysis

Tencent WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval, used to manage knowledge bases across multiple tenants. Prior to version 0.3.0, WeKnora contained a critical authorization bypass vulnerability (CVE-2026-30857) classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The vulnerability exists in the knowledge base copy endpoint, which allows authenticated users to duplicate knowledge bases. Due to insufficient authorization checks, an attacker with low privileges can specify or guess the source knowledge base ID belonging to another tenant and clone it into their own tenant environment. This flaw enables unauthorized access and bulk exfiltration of sensitive document and FAQ content across tenant boundaries. The vulnerability affects confidentiality but does not impact data integrity or system availability. Exploitation requires network access and authentication but no user interaction. The vulnerability has a CVSS 3.1 base score of 5.3, reflecting medium severity due to the need for authentication and high attack complexity. Tencent has addressed this issue in WeKnora version 0.3.0 by implementing proper authorization validation on the copy endpoint to ensure tenant isolation.

Potential Impact

The primary impact of this vulnerability is the unauthorized disclosure of sensitive information stored in knowledge bases across tenants. Organizations using affected versions of WeKnora risk bulk data leakage, which could include proprietary documents, FAQs, or other confidential content. This could lead to competitive disadvantage, intellectual property theft, or exposure of sensitive operational information. Since the vulnerability allows cross-tenant data access, multi-tenant cloud deployments and SaaS providers using WeKnora are particularly at risk. Although the vulnerability does not affect data integrity or availability, the breach of confidentiality can have significant reputational and regulatory consequences, especially for organizations handling sensitive or regulated data. The requirement for authentication limits exposure to insiders or compromised accounts but does not eliminate risk. No known exploits in the wild reduce immediate threat but patching is critical to prevent future attacks.

Mitigation Recommendations

Organizations should immediately upgrade Tencent WeKnora to version 0.3.0 or later, where the authorization bypass vulnerability has been fixed. Until upgrade is possible, restrict access to the knowledge base copy endpoint to only highly trusted users and monitor logs for unusual copy requests or attempts to access knowledge bases belonging to other tenants. Implement strong authentication and account management policies to reduce the risk of compromised credentials being used to exploit this flaw. Conduct regular audits of tenant data access patterns to detect potential unauthorized cloning activities. Network segmentation and application-layer firewalls can help limit exposure of the vulnerable endpoint. Additionally, consider encrypting sensitive knowledge base content at rest and in transit to reduce impact if exfiltration occurs. Finally, maintain an incident response plan to quickly address any detected data leakage incidents.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-05T21:27:35.342Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69ac564fc48b3f10ffb12c2f

Added to database: 3/7/2026, 4:46:07 PM

Last enriched: 3/14/2026, 8:00:46 PM

Last updated: 4/22/2026, 5:01:46 AM

Views: 66

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses