WeKnora vulnerable to SQL Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-22687: 0.38% estimated exploitation activity in the next 30 days; percentile 32.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary After WeKnora enables its Agent service, it allows users to call database query tools. Due to lax code backend verification, attackers can use prompts to bypass query restrictions and obtain sensitive information from the target server and database. Details Source - File: /internal/agent/tools/databasequery.go - Function: validateAndSecureSQL() (lines 249-373) - API Endpoint: POST /api/v1/agent-chat/{sessionid} Sink - File: /internal/agent/tools/databasequery.go - Function: Execute() (line 158: t.db.WithContext(ctx).Raw(securedSQL).Rows()) - Description: Raw SQL execution without parameterized queries 后端校验语句：/internal/agent/tools/databasequery.go, 273-281: 此处存在两处漏洞： 1. 未校验postgres内置危险函数 2. 未考虑//等注释，可替换空格绕过检测 PoC 攻击prompt： <img width="825" height="563" alt="Image" src="https://github.com/user-attachments/assets/ff86ee6f-aa25-4636-958c-c1468d6422c6" / <img width="1666" height="866" alt="Image" src="https://github.com/user-attachments/assets/50ed98fa-532e-4cc7-aa90-5b3ed21523ff"…

Published by the source

9 Jan 2026, 19:19 UTC

Last modified by the source

6 Mar 2026, 14:23 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pcwc-3fw3-8cqv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22687

Advisory: WeKnora vulnerable to SQL Injection
IDs: CVE-2026-22687, GHSA-pcwc-3fw3-8cqv
Record: https://patchnext.com/advisories/cve-2026-22687 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/Tencent/WeKnora 0.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/Tencent/WeKnora: affected < 0.2.5; fixed in 0.2.5

## Suggested inspection (read-only)
- Go github.com/Tencent/WeKnora: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/Tencent/WeKnora.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pcwc-3fw3-8cqv (GitHub-reviewed advisory GHSA-pcwc-3fw3-8cqv lists affected ranges: Go github.com/Tencent/WeKnora >=0 <0.2.5)

Commands are suggestions: review each one before running it.