SQL Injection in praisonai (CVE-2026-40315)
Summary
SQL injection in praisonai (CVE-2026-40315). Risk of unauthorized operations or information disclosure. Exploitable via table_prefix. Mitigation: upgrade to 4.5.133 or later.
Original description
The description as published by the source.
Summary
The table_prefix configuration value is directly used to construct SQL table identifiers without validation.
If an attacker controls this value, they can manipulate SQL query structure, leading to unauthorized data access (e.g., reading internal SQLite tables such as sqlite_master) and tampering with query results.
Details
This allows attackers to inject arbitrary SQL fragments into table identifiers, effectively altering query execution.
This occurs because table_prefix is passed from configuration (from_yaml / from_dict) into SQLiteConversationStore and directly concatenated into SQL queries via f-strings:
sessions_table = f"{table_prefix}sessions"
This value is then used in queries such as:
SELECT * FROM {self.sessions_table}
Since SQL identifiers cannot be safely parameterized and are not validated, attacker-controlled input can modify SQL query structure.
The vulnerability originates from configuration input and propagates through the following flow:
-
Source: config.py
(from_yaml/from_dict) accepts external configuration input -
Propagation: factory.py
(create_stores_from_config) passesconversation_optionsw…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40315 has been found in praisonai.
Attackers can target a specific entry point like table_prefix over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade praisonai to 4.5.133 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-40315" on the vendor's site.
CVE-2026-40315 (praisonai) — CWE-89
Attack surface: table_prefix / sqlite_master / from_yaml / from_dict
Patched: 4.5.133 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in praisonai. Attackers reach the vulnerable code path via table_prefix.
Check the vendor advisory for the affected versions of praisonai. Attack surface: table_prefix / sqlite_master / from_yaml / from_dict.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.5.133.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'praisonai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'praisonai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonai to 4.5.133ステージング環境で 4.5.133 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com