Quick answers
- Is CVE-2026-25574 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25574 being exploited in the wild.
- How severe is CVE-2026-25574?
- Low severity, with a CVSS score of 3.1, published 5 February 2026.
- Which products and versions are affected?
- payload (npm) SEMVER:introduced=0,fixed=3.74.0; Payload CMS < 3.74.0.
- Is there a fix for CVE-2026-25574?
- Yes. payload (npm): upgrade to 3.74.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25574 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-25574?
- Check whether you run payload (npm) or Payload CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- payload (npm): upgrade to 3.74.0 or later
npm install payload@3.74.0
Technical details
The vulnerability is an Insecure Direct Object Reference (IDOR) affecting the payload-preferences internal collection. The root cause is insufficient access control validation in multi-auth collection environments using Postgres or SQLite with default serial/auto-increment IDs. An authenticated user from one auth collection can reference and manipulate preference records belonging to users in different collections by guessing or iterating numeric IDs. Attack requires multiple auth collections, Postgres/SQLite with serial IDs, and users with matching numeric IDs across collections. The attacker needs network access and valid authentication to one collection but gains read/delete capabilities across collections. The vulnerability has been patched in v3.74.0 and does not affect MongoDB-backed deployments or UUID-based ID schemes.
Affected products
- Payload Payload CMS < 3.74.0
Identifiers
- CVE-2026-25574
- GHSA-jq29-r496-r955
Timeline
- 2026-02-05: disclosed
- 2026-02-05: patched: v3.74.0