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-30860: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Tencent WeKnora

0
Critical
VulnerabilityCVE-2026-30860cvecve-2026-30860cwe-89
Published: Sat Mar 07 2026 (03/07/2026, 16:36: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.2.12, a remote code execution (RCE) vulnerability exists in the application's database query functionality. The validation system fails to recursively inspect child nodes within PostgreSQL array expressions and row expressions, allowing attackers to bypass SQL injection protections. By smuggling dangerous PostgreSQL functions inside these expressions and chaining them with large object operations and library loading capabilities, an unauthenticated attacker can achieve arbitrary code execution on the database server with database user privileges. This issue has been patched in version 0.2.12.

AI-Powered Analysis

AILast updated: 03/07/2026, 17:00:34 UTC

Technical Analysis

Tencent WeKnora, an LLM-powered framework for deep document understanding and semantic retrieval, contains a critical SQL injection vulnerability (CVE-2026-30860) in versions prior to 0.2.12. The vulnerability stems from the application's failure to recursively validate child nodes within PostgreSQL array and row expressions during database queries. This improper neutralization of special elements (CWE-89) allows attackers to smuggle dangerous PostgreSQL functions inside these expressions. By chaining these functions with PostgreSQL large object operations and dynamic library loading capabilities, an attacker can escalate the SQL injection to remote code execution (RCE) on the database server. The attack requires no authentication and no user interaction, making it highly exploitable remotely over the network. The database user privileges are leveraged to execute arbitrary code, potentially compromising the entire database server environment. The vulnerability has been patched in WeKnora version 0.2.12. Although no exploits have been reported in the wild, the vulnerability's critical CVSS 3.1 score of 10 reflects its severe impact and ease of exploitation. This flaw highlights the risks of insufficient input validation in complex SQL query constructs, especially when advanced PostgreSQL features are involved.

Potential Impact

The impact of CVE-2026-30860 is severe and wide-ranging. Successful exploitation allows unauthenticated remote attackers to execute arbitrary code on the database server, leading to full compromise of the database environment. This includes unauthorized data disclosure (confidentiality breach), data manipulation or destruction (integrity breach), and potential denial of service (availability breach). Organizations relying on WeKnora for document understanding and semantic retrieval risk exposure of sensitive information and disruption of critical services. Since the attack requires no authentication and can be performed remotely, the threat surface is large. Compromise of the database server could also serve as a pivot point for further attacks within the network. The critical CVSS score underscores the urgency for remediation. Enterprises using affected versions face potential regulatory, reputational, and operational risks if exploited.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade Tencent WeKnora to version 0.2.12 or later, where the issue is patched. In addition, it is crucial to implement strict database access controls, ensuring that the database user account used by WeKnora has the minimum necessary privileges, ideally avoiding superuser or elevated rights that could facilitate code execution. Employ network segmentation and firewall rules to restrict access to the database server only to trusted hosts. Enable database logging and monitoring to detect suspicious queries or unusual large object operations indicative of exploitation attempts. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious PostgreSQL function calls embedded in queries. Regularly audit and test input validation mechanisms, especially for complex SQL constructs like arrays and row expressions. Finally, maintain an incident response plan to quickly address any signs of compromise.

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: 69ac564fc48b3f10ffb12c38

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

Last enriched: 3/7/2026, 5:00:34 PM

Last updated: 3/8/2026, 3:31:03 AM

Views: 9

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

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