Payload has a CSRF Protection Bypass in Authentication Flow

published 2026-04-01 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-18017 , GHSA-p6mr-xf3r-ghq4

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits: 0; none known

Payload 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.

Patch / fix

fixed in 2 links 1

npm payload 3.79.1
payloadcms payload 3.79.1

github.com/payloadcms/payload/releases/tag/v3.79.1 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 7 mo ago (2026-04-02)

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
GitHub	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	payload	<3.79.1	3.79.1

Affected products

payloadcms payload

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

github.com /payloadcms/payload/security/advisories/GHSA-p6mr-xf3r-ghq4
web, mitigation, vendor-advisory
github.com /payloadcms/payload/releases/tag/v3.79.1
web, product, release-notes
nvd.nist.gov /vuln/detail/CVE-2026-34749
advisory
github.com /payloadcms/payload
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary