{"answers":{"affected":"2 open source packages ship an affected version, including payload. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34749 in the wild and no public exploit code.","fix":"Upgrade payload to 3.79.1 or later.","what":"CVE-2026-34749 is a medium-severity vulnerability in payloadcms payload, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-34749 and fix it if it is affected.\n\nWhat it is: CVE-2026-34749 is a medium-severity vulnerability in payloadcms payload, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-34749 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- payload (npm): affected all versions; fixed in 3.79.1\n- payload (npm): affected all versions; fixed in 3.79.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34749/ (Markdown: https://insights.sbomify.com/CVE-2026-34749/index.md)","id":"CVE-2026-34749","markdown":"https://insights.sbomify.com/CVE-2026-34749/index.md","name":"CVE-2026-34749","record":{"aliases":["GHSA-p6mr-xf3r-ghq4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Headless CMS","requires_auth":"none","summary":"Attackers can bypass CSRF protection in the authentication flow under certain conditions, allowing unauthorized cross-site requests.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"payload","vendor":"payloadcms"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Payload has a CSRF Protection Bypass in Authentication Flow","id":"CVE-2026-34749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints","id":"CVE-2026-34750"},"packages":[{"ecosystem":"npm","fixed":["3.79.1"],"introduced":["0"],"last_affected":[],"package":"payload","purl":null,"source":"GHSA-p6mr-xf3r-ghq4"},{"ecosystem":"npm","fixed":["3.79.1"],"introduced":["0"],"last_affected":[],"package":"payload","purl":"pkg:npm/payload","source":"GHSA-p6mr-xf3r-ghq4"}],"prev":{"headline":"@payloadcms/next has Stored XSS in Admin Panel","id":"CVE-2026-34748"},"products":["payload"],"published":"2026-04-01","related":[{"cvss_score":10,"headline":"Payload: RCE in Payload Form Builder","id":"CVE-2026-105857","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Payload: Unauthorized update to collection documents","id":"CVE-2026-105859","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Payload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite Adapters","id":"CVE-2026-25544","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":9.8,"headline":"Unrestricted Upload of File with Dangerous Type in Payload","id":"CVE-2022-27952","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":9.3,"headline":"Payload: Field access control bypass on auth collections","id":"CVE-2026-105851","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.2,"headline":"Payload authentication token field handling issue","id":"CVE-2026-105863","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.1,"headline":"Payload has Unvalidated Input in Password Recovery Endpoints","id":"CVE-2026-34751","kev_date_added":null,"published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-06","vendors":["payloadcms"]},"summary":"Attackers can bypass CSRF protection in the authentication flow under certain conditions, allowing unauthorized cross-site requests.","url":"https://insights.sbomify.com/CVE-2026-34749/"}