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.
Original description
The description as published by the source.
Summary of CVE-2026-22599 Vulnerability Details
- CVE: CVE-2026-22599
- CVSS v3.1 Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N(9.3 — Critical) - Affected Versions:
@strapi/content-type-builder<=5.33.1 (v5),@strapi/plugin-content-type-builder<=4.26.0 (v4) - How to Patch: Immediately update your Strapi to >=5.33.2 (v5) or >=4.26.1 (v4)
Description of CVE-2026-22599
A database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated administrator could inject arbitrary database statements through the column.defaultTo attribute when creating or modifying a content type. Setting defaultTo as a tuple [value, { isRaw: true }] caused the value to be passed directly into Knex's db.connection.raw() during schema migration without sanitization, allowing arbitrary statement execution at the database layer. Depending on the database engine, this enabled arbitrary file read via database utility functions, denial of service via forced server crash on schema-migration error, and on engines that permit external program execution, remote code execution against the database server.
The patch addresses this by restricting all Content-Type Builder write APIs to development mode only. Production deployments running v5.33.2 or later return 404 for requests against /content-type-builder/content-types and related endpoints, removing the network-reachable attack surface entirely.
IoC's for CVE-2…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-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.
SQL injection (CWE-89) exists in @strapi/content-type-builder. Attackers reach the vulnerable code path via column.defaultTo.
Check the vendor advisory for the affected versions of @strapi/content-type-builder. Attack surface: column.defaultTo / defaultTo / passwd / etc.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 5.33.2.
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 '@strapi/content-type-builder' . 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 '@strapi/content-type-builder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@strapi/content-type-builderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @strapi/content-type-builder to 5.33.2ステージング環境で 5.33.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com