Payload: Token refresh and password reset responses may expose restricted user fields
What fixes it
- 3.90.0payload, npmGitHub
npm install payload@3.90.0 - 4.0.0-canary.34payload, npmGitHub
npm install payload@4.0.0-canary.34
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Impact
Token refresh and password reset responses could return fields that the requesting user did not have access to.
You are affected if:
- An authentication collection contains hidden or read-restricted fields.
Patches
Authentication responses now apply field access and hidden-field filtering before returning user documents. Full user documents remain available server-side for access control.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Custom authentication strategies remain responsible for filtering user documents returned through custom responses.
Workarounds
There is no complete workaround. Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Text from GitHub Advisory Database
Affected versions 6
- payload, npm>= 3.0.0, < 3.90.0GitHub
- payload, npm>= 4.0.0-canary.0, < 4.0.0-canary.34GitHub
- payloadaffected: >= 3.0.0, < 3.90.0CVE List
- payloadaffected: >= 4.0.0-canary.0, < 4.0.0-canary.34CVE List
- payload, npmfrom 3.0.0, fixed in 3.90.0OSV
- payload, npmfrom 4.0.0-canary.0, fixed in 4.0.0-canary.34OSV
References 4
- github.com/payloadcms/payload/commit/f5f1283d275c58b30e2faa6be7cdc4d49451ea91Fixvia CVE List
- github.com/payloadcms/payload/releases/tag/v3.90.0Fixvia CVE List
- github.com/payloadcms/payload/security/advisories/GHSA-xgv3-crq2-6f69Advisoryvia CVE List
- github.com/advisories/GHSA-xgv3-crq2-6f69Advisoryvia GitHub