LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22687: WeKnora vulnerable to SQL Injection

WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, after WeKnora enables the Agent service, it allows users to call the database query tool. Due to insufficient backend validation, an attacker can use prompt‑based bypass techniques to evade query restrictions and obtain sensitive information from the target server and database. This issue has been patched in version 0.2.5.

MediumCVSS 5.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22687 affects Tencent WeKnora before 0.2.5. When the Agent service is enabled, users may be able to bypass query restrictions through prompts and access sensitive server or database information. The vendor states the issue is fixed in 0.2.5. No provided source indicates active exploitation.

Executive priority

Prioritize patching WeKnora systems that handle sensitive documents or connect to sensitive databases. This is not a confirmed exploited emergency, but it can expose confidential data if the vulnerable Agent workflow is enabled.

Technical view

This is a CWE-89 SQL injection issue in WeKnora’s Agent database query tool. Insufficient backend validation can allow prompt-based bypass of query restrictions. CVSS 3.1 is 5.6: network exploitable, high complexity, no privileges or user interaction, with low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Tencent WeKnora deployments before version 0.2.5 where the Agent service and database query tool are enabled or reachable by users.

Exploitation context

The source describes prompt-based bypass techniques but does not provide evidence of public exploitation. It is not listed as KEV. Exploitation is rated high complexity, but could still matter where WeKnora connects to sensitive databases.

Researcher notes

The public evidence is limited to the CVE record, GitHub advisory, and linked commit. Avoid assuming impact outside Tencent WeKnora <0.2.5. Validate exposure by configuration, not just package presence, because the described path requires Agent service enablement.

Mitigation direction

  • Upgrade Tencent WeKnora to version 0.2.5 or later.
  • Review the GitHub advisory for vendor-specific remediation guidance.
  • If upgrade is delayed, evaluate limiting Agent service access until patched.
  • Restrict access to database query functionality to trusted users only.

Validation and detection

  • Inventory WeKnora deployments and record installed versions.
  • Confirm whether the Agent service is enabled.
  • Confirm whether database query tooling is exposed to users.
  • Verify version 0.2.5 or the referenced fix is deployed.
  • Review logs for unusual Agent-driven database query activity.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22687 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L2.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.6Medium
CVSS 3.1 vector shape for CVE-2026-22687Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TencentWeKnora< 0.2.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.