CVE-2026-34749
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.79.1, a Cross-Site Request Forgery (CSRF) vulnerability exists in the authentication flow. Under certain conditions, the configured CSRF protection could be bypassed, allowing cross-site requests to be made. This issue has been patched in version 3.79.1.
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 confidencePayload CMS versions before 3.79.1 contain a CSRF vulnerability in the authentication flow where configured CSRF protection can be bypassed under certain conditions, allowing malicious cross-site requests to be made.
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.79.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 Payload CMS version in package.jsonLocate the package.json file in your Payload CMS project root and look for the 'payload' dependency version entryAffected if The version listed is less than 3.79.1 (e.g., 3.79.0, 3.78.0, etc.)
-
Check Payload CMS version via npmRun 'npm list payload' or 'yarn list payload' in your project directory to see the installed versionAffected if The installed version shown is before 3.79.1
-
Verify CSRF protection is configuredExamine your Payload CMS configuration file (typically payload.config.ts or similar) for CSRF-related settings, typically under the 'csrf' configuration optionAffected if CSRF protection is explicitly configured and enabled in your config, and the Payload version is below 3.79.1
-
Check for custom CSRF middlewareInspect your project for any custom middleware or plugins that handle CSRF protection, typically in a middleware or hooks directoryAffected if Custom CSRF middleware exists and the Payload version is below 3.79.1
You are affected if your installed Payload CMS version is below 3.79.1 AND you have CSRF protection configured or rely on Payload's built-in CSRF protection in the authentication flow.
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.79.1
Upgrade Payload CMS to version 3.79.1 or later to patch the CSRF bypass vulnerability in the authentication flow.
Payload CMS version 3.79.1
- Ensure you have a complete backup of your current Payload CMS installation and database
- Review the Payload 3.79.1 release notes for any changes relevant to your installation
- Update your package.json dependency to specify "payload": "^3.79.1" or the exact version "3.79.1"
- Run your package manager's update command (e.g., npm install, yarn install, or pnpm install) to fetch version 3.79.1
- After updating dependencies, run any necessary database migrations if required by the release notes
- Restart your Payload CMS application
- Verify that the application is running correctly and test authentication flows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34749 — 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-34749 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