EUVD-2026-97320
GHSA-36w2-ffqw-gx86
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to WeKnora with low-priv account
-
DeliverySubmit crafted subquery via API
-
ExploitBypass validateSubquery SQL Validator
-
ExecutionExecute injected SQL on backend DB
-
ImpactDisclose or alter limited data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated low-privileged account (CVSS PR:L) able to reach the WeKnora application over the network and submit input that flows into the SQL Validator's subquery validation path (validateSubquery in internal/utils/inject.go). The core prerequisite is the ability to craft a subquery that bypasses WeKnora's own SQL validation logic on versions up to and including 0.8.1. Limiting factors: valid credentials are needed (not unauthenticated), impact is constrained to Low per the vendor vector, and instances on 0.8.2 or later are not affected. No special non-default configuration is indicated in the description. |
| Impact | This is a low-priority issue despite being a remotely reachable SQL injection (CWE-89). The vendor's CVSS 4.0 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable but authenticated flaw (PR:L) with only Low vulnerable-system impact across confidentiality, integrity, and availability (VC:L/VI:L/VA:L) and no subsequent-system impact, yielding a base score of just 2.1. The signals are largely consistent rather than conflicting: the E:P (Proof-of-Concept) exploit-maturity value aligns with the confirmed publicly available exploit code (a gist plus a write-up), but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of widespread or automated exploitation. The low impact scoring is notable for a SQL injection - it suggests the flaw is a partial bypass of WeKnora's SQL Validator (a subquery validation weakness) rather than full database compromise, which is plausible given the affected function is validateSubquery. Net assessment: a genuine but low-severity, authentication-gated bug in a niche open-source product; patch on a normal cycle rather than treating as an emergency. Note that the provided GitHub PR diff does not actually show the validateSubquery/inject.go change (it shows signing-key and CI changes), so the exact fix content could not be independently confirmed from the supplied source evidence. |
| Exploit ScenarioDerived | An attacker who already holds valid low-privileged credentials to a WeKnora instance submits a crafted subquery that evades the SQL Validator in validateSubquery, injecting SQL that the application executes against its backend database. Public exploit code exists (a k4z01 gist and a 'WeKnora-SQL-Validation-Bypass' write-up), lowering the effort to reproduce. Because the CVSS impact is rated Low across C/I/A, realistic outcomes are limited data disclosure or manipulation rather than full database takeover. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
SQL injection in Tencent WeKnora through version 0.8.1 allows an authenticated, low-privileged remote attacker to bypass the platform's own SQL Validator by crafting a malicious subquery that is mishandled by the validateSubquery function in internal/utils/inject.go, manipulating backend database queries. Publicly available exploit code exists, including a proof-of-concept write-up and a public gist, so exploitation is practical for anyone with valid credentials, though the assessed impact is limited to Low confidentiality, integrity, and availability per the vendor vector; no confirmed active exploitation (CISA KEV) has been recorded. The issue carries a very low CVSS 4.0 base score of 2.1 and is a low-priority issue despite being a remotely reachable SQL injection (CWE-89).
RemediationAI
Upgrade Tencent WeKnora to version 0.8.2, which is the vendor-released fix for CVE-2026-108821 (release notes: https://github.com/Tencent/WeKnora/releases/tag/v0.8.2); the specific fix is identified by commit d7ccd5ba517cc3968e6d5000a2ab0f4b51ef1dda and the associated pull request https://github.com/Tencent/WeKnora/pull/3305. Until every instance is upgraded, restrict WeKnora write/query endpoints to trusted authenticated users and reduce the number of accounts holding even low-privileged roles, since exploitation requires a valid session (PR:L); note that this only shrinks the attack surface and does not eliminate the validator bypass. Where possible, place a WAF or API gateway rule in front of the application to detect and block obvious subquery tampering patterns, accepting the trade-off of potential false positives on legitimate complex queries. Treat any authenticated user as a potential injection source and monitor database logs for anomalous subquery constructs originating from the platform, recognizing that detection is retroactive and not a substitute for patching. No vendor workaround is documented, so patching to 0.8.2 remains the only complete mitigation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is WeKnora's SQL Validator, a defensive layer intended to inspect and reject dangerous SQL - particularly within subqueries - before it reaches the database. CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) is the root-cause class: the validateSubquery routine in internal/utils/inject.go fails to correctly parse or neutralize attacker-controlled subquery input, so injected SQL fragments survive validation. Because the flaw lives in the validator itself rather than in a single query builder, a bypass undermines the component's security guarantee across any code path that relies on it. The CPE cpe:2.3:a:tencent:weknora:*:*:*:*:*:*:*:* is version-wildcarded, and the advisory explicitly bounds affected releases at 0.8.1 and below, with 0.8.2 introducing the fix. Attack is network-reachable (AV:N) but requires a low-privileged authenticated session (PR:L), and the impact is constrained to Low across confidentiality, integrity, and availability in both the vendor CVSS 4.0 vector and the independent CVSS 3.1 assessment.
Know when Tencent gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Network-reachable injection with low attack complexity; PR:L because a valid low-privileged account is required per the vendor vector; validator bypass yields limited C/I/A impact, so all set Low.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in Tencent WeKnora up to 0.8.1. Impacted is the function validateSubquery of the file internal/utils/inject.go of the component SQL Validator. The manipulation leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 0.8.2 is recommended to address this issue. The identifier of the patch is d7ccd5ba517cc3968e6d5000a2ab0f4b51ef1dda. It is recommended to upgrade the affected component.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
WeKnora LLM framework (before 0.2.5) allows authenticated users to inject MCP stdio commands that the server executes as
OS command injection in WeKnora from version 0.2.5 allows authenticated users to execute arbitrary system commands. CVSS
SQL injection in WeKnora LLM document understanding framework allows authenticated users to extract arbitrary database c
vConsole v3.15.0 was discovered to contain a prototype pollution due to incorrect key and value resolution in setOptions
Insufficient authorization checks in WeKnora's tenant management endpoints allow any authenticated user to read, modify,
Insecure Permissions vulnerability in Tencent wechat v.8.0.37 allows an attacker to escalate privileges via the web-view
Tencent Blueking CMDB v3.2.x to v3.9.x was discovered to contain a Server-Side Request Forgery (SSRF) via the event subs
Tencent GameLoop before 4.1.21.90 downloaded updates over an insecure HTTP connection. Rated high severity (CVSS 8.1), t
In Tencent QQ through 9.7.8.29039 and TIM through 3.4.7.22084, QQProtect.exe and QQProtectEngine.dll do not validate poi
HaboMalHunter through 2.0.0.3 in Tencent Habo allows attackers to evade dynamic malware analysis via PIE compilation. Ra
Tencent tdsqlpcloud through 1.8.5 allows unauthenticated remote attackers to discover database credentials via an index.
A vulnerability in the lua parser of TscanCode tsclua v2.15.01 allows attackers to cause a Denial of Service (DoS) via a
Exploit-DB