CVE-2026-34748
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 · uneditedPayload is a free and open source headless content management system. Prior to version 3.78.0 in @payloadcms/next, a stored Cross-Site Scripting (XSS) vulnerability existed in the admin panel. An authenticated user with write access to a collection could save content that, when viewed by another user, would execute in their browser. This issue has been patched in version 3.78.0.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Payload CMS admin panel allows authenticated users with write access to inject malicious scripts into content that executes when other users view the content. The vulnerability affects @payloadcms/next versions prior to 3.78.0.
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< 3.78.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
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.
-
Check @payloadcms/next versionRun `npm list @payloadcms/next` or inspect your package.json dependencies section to identify the installed version of @payloadcms/nextAffected if Installed version is lower than 3.78.0
-
Check Payload CMS versionRun `npm list payloadcms` or inspect your package.json dependencies section to identify the installed version of the payload packageAffected if Installed version is lower than 3.78.0
-
Verify admin panel accessibilityConfirm the Payload admin panel endpoint is accessible over the network. Check your middleware and authentication configuration to determine if the admin panel can be reached by authenticated usersAffected if Admin panel is exposed and accessible without proper access restrictions
-
Identify write-access usersReview user roles and permissions in the Payload admin panel under Settings > Users or Collections. Check which users have create or update permissions on content collectionsAffected if One or more users have write access to collections, allowing them to insert content that could contain malicious scripts
-
Inspect stored content for XSS payloadsExamine content entries in your collections, particularly fields that accept rich text, HTML, or code input. Look for script tags, event handlers (onclick, onerror, etc.), or other suspicious JavaScript patterns in stored dataAffected if Content entries contain unsanitized script tags or event handlers that could execute when viewed by other users
You are affected if you are running @payloadcms/next or Payload CMS version lower than 3.78.0 and your admin panel is accessible to users with write permissions to content collections.
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 · scoped3.78.0
Upgrade @payloadcms/next to version 3.78.0 or later to apply the patched code. Review existing content in collections for any existing malicious payloads.
@payloadcms/next version 3.78.0
- Check your current Payload version by running `npm list @payloadcms/next` or checking package.json
- Update Payload to version 3.78.0 by running `npm install @payloadcms/[email protected]` or `pnpm update @payloadcms/[email protected]`
- Run `npm install` or `pnpm install` to ensure all dependencies are updated
- Restart your development server and verify the admin panel loads correctly
- Test that the XSS vulnerability is no longer present by attempting to save and retrieve a payload containing script tags in any field
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34748 — 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-34748 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