CVE-2026-25574: Payload Affected by Cross-Collection IDOR in payload-preferences Access Control (Multi-Auth Environments)

Published Feb 5, 2026
·
Updated

Impact

A cross-collection Insecure Direct Object Reference (IDOR) vulnerability exists in the payload-preferences internal collection. In multi-auth collection environments using Postgres or SQLite with default serial/auto-increment IDs, authenticated users from one auth collection can read and delete preferences belonging to users in different auth collections when their numeric IDs collide.

Users are affected if ALL of these are true:

- Multiple auth collections configured (e.g., admins + customers) - Postgres or SQLite database adapter with serial/auto-increment IDs - Users in different auth collections with the same numeric ID

Not affected:

- @payloadcms/db-mongodb adapter - Single auth collection environments - Postgres/SQLite with idType: 'uuid'

Patches

This vulnerability has been patched in v3.74.0. Users should upgrade to v3.74.0 or later.

Workarounds

There is no workaround other than upgrading. Users with multiple auth collections using Postgres or SQLite with serial IDs should upgrade immediately.

Other sources

Payload is a free and open source headless content management system. Prior to 3.74.0, a cross-collection Insecure Direct Object Reference (IDOR) vulnerability exists in the payload-preferences internal collection. In multi-auth collection environments using Postgres or SQLite with default serial/auto-increment IDs, authenticated users from one auth collection can read and delete preferences belonging to users in different auth collections when their numeric IDs collide. This vulnerability has been patched in v3.74.0.

— MITRE

Affected Software

2 affected componentsFixes available
npm/payload<3.74.0
3.74.0
PayloadCMS Payload Node.js<3.74.0

Event History

Feb 5, 2026
Advisory Published
via GitHub·09:02 PM
Data Sourced
via GitHub·09:02 PM
DescriptionSeverityWeaknessAffected Software
Feb 6, 2026
CVE Published
via MITRE·09:04 PM
Data Sourced
via MITRE·09:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
Affected Software
May 15, 58112
Event
via FIRST·10:40 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-25574?

CVE-2026-25574 is considered a high severity vulnerability due to its potential for unauthorized data access.

2

How do I fix CVE-2026-25574?

To fix CVE-2026-25574, upgrade to the latest version of the 'payload' package, which is 3.74.0 or higher.

3

What platforms are affected by CVE-2026-25574?

CVE-2026-25574 affects applications using the 'payload' package with PostgreSQL or SQLite configured with default serial/auto-increment IDs.

4

What type of vulnerability is CVE-2026-25574?

CVE-2026-25574 is classified as a cross-collection Insecure Direct Object Reference (IDOR) vulnerability.

5

Who is impacted by CVE-2026-25574?

Authenticated users from one authorization collection can be impacted, allowing them to access unauthorized data in a multi-auth collection environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203