Impact
When querying JSON or richText fields, user input was directly embedded into SQL without escaping, enabling blind SQL injection attacks. An unauthenticated attacker could extract sensitive data (emails, password reset tokens) and achieve full account takeover without password cracking.
You are affected if ALL of these are true:
- Payload version < v3.73.0
- Using a Drizzle-based database adapter (
@payloadcms/drizzle as dependency):
@payloadcms/db-postgres@payloadcms/db-vercel-postgres@payloadcms/db-sqlite@payloadcms/db-d1-sqlite
- At least one accessible collection that has a
type: 'json' or type: 'richText' field where access.read returns anything other than false (true or Where constraint)
You are NOT affected if:
- Using
@payloadcms/db-mongodb
- No JSON or richText fields exist in any collection
- All JSON/richText fields have
access: { read: () => false }
Patches
Upgrade to Payload v3.73.0 or later.
Workarounds
If you cannot upgrade immediately, add access: { read: () => false } to all JSON and richText fields as a temporary mitigation.
Impact
When querying JSON or richText fields, user input was directly embedded into SQL without escaping, enabling blind SQL injection attacks. An unauthenticated attacker could extract sensitive data (emails, password reset tokens) and achieve full account takeover without password cracking.
You are affected if ALL of these are true:
@payloadcms/drizzleas dependency):@payloadcms/db-postgres@payloadcms/db-vercel-postgres@payloadcms/db-sqlite@payloadcms/db-d1-sqlitetype: 'json'ortype: 'richText'field whereaccess.readreturns anything other thanfalse(trueorWhereconstraint)You are NOT affected if:
@payloadcms/db-mongodbaccess: { read: () => false }Patches
Upgrade to Payload v3.73.0 or later.
Workarounds
If you cannot upgrade immediately, add
access: { read: () => false }to all JSON and richText fields as a temporary mitigation.