← Back
CVE-2023-25171
Vulnerability in kiwitcms (CVE-2023-25171)
Summary
vulnerability in kiwitcms (CVE-2023-25171). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `12.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-25171** has been found in kiwitcms.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade kiwitcms to **12.0** or later.
If unsure, ask your IT team or search "kiwitcms CVE-2023-25171" on the vendor's site.
CVE-2023-25171 (kiwitcms) — CWE-770 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `12.0` — apply immediately
Workaround: Users may install and configure a rate-limiting proxy in front of Kiwi TCMS such as Nginx and/or configure rate limits on their email server when possible.
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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in kiwitcms.
📍 Affected scope
kiwitcms — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **12.0**.
🛡️ Workaround
Workaround: Users may install and configure a rate-limiting proxy in front of Kiwi TCMS such as Nginx and/or configure rate limits on their email server when possible.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'kiwitcms' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kiwitcms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `kiwitcms` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Users may install and configure a rate-limiting proxy in front of Kiwi TCMS such as Nginx and/or configure rate limits on their email server when possible.パッチが適用されるまでの応急処置として、Users may install and configure a rate-limiting proxy in front of Kiwi TCMS such as Nginx and/or configure rate limits on their email server when possible. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade kiwitcms to 12.0ステージング環境で 12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
kiwitcms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-25171
- advisory https://github.com/advisories/GHSA-7j9h-3jxf-3vrf
- package https://github.com/kiwitcms/Kiwi
- package https://pypi.org/project/kiwitcms
- web https://github.com/kiwitcms/Kiwi/security/advisories/GHSA-7j9h-3jxf-3vrf
- web https://github.com/kiwitcms/Kiwi/commit/761305d04f5910ba14cc04d1255a8f1afdbb87f3
- web https://huntr.dev/bounties/3b712cb6-3fa3-4f71-8562-7a7016c6262e
- web https://kiwitcms.org/blog/kiwi-tcms-team/2023/02/15/kiwi-tcms-120