Payload is a free and open source headless content management system. Prior to 3.90.0 and 4.0.0-canary.34, an attacker with read and create or update access to a collection containing a json field or a blocks field with blocksAsJSON enabled can inject SQL through a crafted field path and operators. Collections without those fields are not affected, and richText fields are not affected. The SQLite packages are fixed in versions 3.90.0 and 4.0.0-canary.34, and the Postgres packages are fixed in version 3.73.0.

Affected: npm: @payloadcms/db-sqlite, npm: @payloadcms/db-d1-sqlite, npm: @payloadcms/db-postgres, npm: @payloadcms/db-vercel-postgres

### Impact

An attacker who has read plus create or update access to a collection can submit a request that includes a SQL injection targeting a specific field path shape and operators in Payload's SQLite and Postgres.

#### You are affected if:

- You use `@payloadcms/db-sqlite` or `@payloadcms/db-d1-sqlite`. - You use `@payloadcms/db-postgres` or `@payloadcms/db-vercel-postgres` `< 3.73.0`. - A readable collection has a `json` field, or a` blocks` field with `blocksAsJSON: true`. - The attacker has read plus create or update access on it.

#### You are not affected if: - You have no `json or `blocksAsJSON` fields. `richText` is not affected. - You run a patched version.

### Patches

The patched version sanitizes the query input to prevent injection.

Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.