# CVE-2026-25544: Payload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite Adapters

> Unauthenticated attackers can perform blind SQL injection via JSON/RichText queries to extract sensitive data and achieve full account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-xx6w-jxg9-2wh8

## What is CVE-2026-25544?

CVE-2026-25544 is a critical SQL injection vulnerability in payloadcms payload, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Payload is a free and open source headless content management system. Prior to 3.73.0, 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. This vulnerability is fixed in 3.73.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-25544?

2 open source packages ship an affected version, including @payloadcms/drizzle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@payloadcms/drizzle` | npm | All versions | 3.73.0 |
| `@payloadcms/drizzle` | npm | All versions | 3.73.0 |

Products: Payloadcms Payload.

## How do I fix CVE-2026-25544?

Upgrade @payloadcms/drizzle to 3.73.0 or later.

## Is CVE-2026-25544 being exploited?

There is no known exploitation of CVE-2026-25544 in the wild and no public exploit code.

Public exploit code:

- Payload CMS 3.72.0 - Blind SQL Injection (exploitdb)

## Other vulnerabilities in payloadcms payload

- [CVE-2026-105857](https://insights.sbomify.com/CVE-2026-105857/): Payload: RCE in Payload Form Builder (critical 10.0)
- [CVE-2026-105859](https://insights.sbomify.com/CVE-2026-105859/): Payload: Unauthorized update to collection documents (critical 9.8)
- [CVE-2022-27952](https://insights.sbomify.com/CVE-2022-27952/): Unrestricted Upload of File with Dangerous Type in Payload (critical 9.8)
- [CVE-2026-105851](https://insights.sbomify.com/CVE-2026-105851/): Payload: Field access control bypass on auth collections (critical 9.3)
- [CVE-2026-105863](https://insights.sbomify.com/CVE-2026-105863/): Payload authentication token field handling issue (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25544 and fix it if it is affected.

What it is: CVE-2026-25544 is a critical SQL injection vulnerability in payloadcms payload, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25544 in the wild and no public exploit code.

Affected packages and fixed versions:
- @payloadcms/drizzle (npm): affected all versions; fixed in 3.73.0
- @payloadcms/drizzle (npm): affected all versions; fixed in 3.73.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25544/ (Markdown: https://insights.sbomify.com/CVE-2026-25544/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25544
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25544
- OSV: https://osv.dev/vulnerability/CVE-2026-25544

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25544/
Summaries are generated and may contain mistakes; the official description above is the record.