← Back
CVE-2026-22599
high
CVSS 7.2
SQL Injection in @strapi/content-type-builder (CVE-2026-22599)
Summary
SQL injection in @strapi/content-type-builder (CVE-2026-22599). Successful exploitation can lead to full system takeover. Exploitable via ``column.defaultTo``. Mitigation: upgrade to `5.33.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-22599** has been found in @strapi/content-type-builder.
Attackers can target a specific entry point like ``column.defaultTo`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade @strapi/content-type-builder to **5.33.2** or later.
If unsure, ask your IT team or search "@strapi/content-type-builder CVE-2026-22599" on the vendor's site.
CVE-2026-22599 (@strapi/content-type-builder) — CWE-89 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `column.defaultTo` / `defaultTo` / `passwd` / `etc`
Patched: `5.33.2` — 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.
❓ What is the problem
**SQL injection** (CWE-89) exists in @strapi/content-type-builder. Attackers reach the vulnerable code path via ``column.defaultTo`` without authentication.
📍 Affected scope
@strapi/content-type-builder — . Attack surface: `column.defaultTo` / `defaultTo` / `passwd` / `etc`.
🔥 Severity
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.33.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@strapi/content-type-builder' .` 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 '@strapi/content-type-builder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@strapi/content-type-builder` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @strapi/content-type-builder to 5.33.2ステージング環境で 5.33.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@strapi/content-type-builder
[{"type":"SEMVER","events":[{"introduced":"5.0.0"},{"fixed":"5.33.2"}]}]
npm
@strapi/plugin-content-type-builder
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.26.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-22599
- package https://github.com/strapi/strapi
- web https://github.com/strapi/strapi/security/advisories/GHSA-3xcq-8mjw-h6mx
- web https://github.com/strapi/strapi/releases/tag/v4.26.1
- web https://github.com/strapi/strapi/releases/tag/v5.33.2
- web https://github.com/advisories/GHSA-3xcq-8mjw-h6mx