npm package report

Is @strapi/plugin-content-type-builder safe?

1 known vulnerability, worst severity CRITICAL.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


      cvss
      0.0
      critical

      severity out of 10

      epss
      0.00%
      medium

      chance of exploitation in 30 days, 66th percentile of all CVEs

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-3xcq-8mjw-h6mx, the advisory selected below

      // 1 advisories

      GHSA-3xcq-8mjw-h6mx

      CRITICALCVE-2026-22599
      // 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.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-2026-22599

      Indicators that an instance running an unpatched version may have been exploited:

      • HTTP access logs containing POST or PUT requests to /content-type-builder/content-types from a non-internal source. Regex pattern: (POST|PUT)\s+/content-type-builder/
      • Database server logs containing unexpected DEFAULT clause values that reference filesystem-access or program-execution helper functions of your database engine
      • Strapi server crashes immediately following a content-type creation or update, observed as the Node process exiting during the schema-migration step
      • Files appearing under unexpected paths on the database host that match content-type DEFAULT values from the application
      • Newly-created content-types named or shaped to extract specific data (attribute names like passwd, etc, env, config)
      // cvss v4.0 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

      Attack vector
      Network
      Attack complexity
      Low
      Attack requirements
      None
      Privileges required
      High
      User interaction
      None
      Confidentiality (vulnerable system)
      High
      Integrity (vulnerable system)
      High
      Availability (vulnerable system)
      None
      Confidentiality (subsequent systems)
      High
      Integrity (subsequent systems)
      High
      Availability (subsequent systems)
      None

      Checked 2026-09-27 at 21:36 UTC. The most recent advisory here was published 2026-05-13. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.