CVE-2026-39397
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited@delmaredigital/payload-puck is a PayloadCMS plugin for integrating Puck visual page builder. Prior to 0.6.23, all /api/puck/* CRUD endpoint handlers registered by createPuckPlugin() called Payload's local API with the default overrideAccess: true, bypassing all collection-level access control. The access option passed to createPuckPlugin() and any access rules defined on Puck-registered collections were silently ignored on these endpoints. This vulnerability is fixed in 0.6.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe @delmaredigital/payload-puck plugin for PayloadCMS had a critical access control bypass in all /api/puck/* CRUD endpoints. These endpoints used Payload's local API with overrideAccess: true as a default, silently ignoring both the access option passed to createPuckPlugin() and any collection-level access rules defined on Puck-registered collections. This allowed unauthenticated or unauthorized users to bypass all access controls on affected endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.6.23CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of @delmaredigital/payload-puckRun 'npm list @delmaredigital/payload-puck' or check the package.json dependencies for @delmaredigital/payload-puckAffected if The version listed is less than 0.6.23 (e.g., 0.6.22, 0.6.0, etc.)
-
Confirm the plugin is registered in the Payload configExamine your Payload config file (usually payload.config.ts) for the '@delmaredigital/payload-puck' plugin import and registrationAffected if The plugin is registered and active in the Payload configuration
-
Identify collections exposed via PuckLook at the Puck plugin configuration in your payload.config.ts to see which collections are registered with PuckAffected if Any collections are registered with the Puck plugin for CRUD operations via /api/puck/* endpoints
-
Check if access controls exist on Puck-registered collectionsReview the access controls (read, update, delete, create) defined in the collection configuration for each Puck-registered collection in your configAffected if The collections have access rules defined but the /api/puck/* endpoints will bypass them due to the overrideAccess: true behavior in the plugin
You are affected if you have @delmaredigital/payload-puck version less than 0.6.23 installed AND have collections registered with the Puck plugin.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.6.23
Upgrade @delmaredigital/payload-puck to version 0.6.23 or later to apply the fix that removes the insecure default overrideAccess: true setting.
0.6.23
- Check the current version of @delmaredigital/payload-puck in your project dependencies (package.json or package-lock.json)
- Upgrade the package to version 0.6.23 or later using your package manager (e.g., npm install @delmaredigital/[email protected], yarn add @delmaredigital/[email protected], or pnpm add @delmaredigital/[email protected])
- Run your package manager's install/update command to ensure dependencies are resolved
- Test that the /api/puck/* endpoints now respect collection-level access controls defined in your PayloadCMS configuration
- Verify that unauthorized users can no longer access or modify Puck-registered collection data through these endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39397 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data