{"answers":{"affected":"4 open source packages ship an affected version, including statamic/cms.","exploited":"There is no known exploitation of CVE-2026-71434 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to a fixed version for your release line: 5.74.3 or 6.24.2.","what":"CVE-2026-71434 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71434 and fix it if it is affected.\n\nWhat it is: CVE-2026-71434 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71434 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected all versions; fixed in 5.74.3\n- statamic/cms (Packagist): affected all versions; fixed in 5.74.3\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.2\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.2\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-71434/ (Markdown: https://insights.sbomify.com/CVE-2026-71434/index.md)","id":"CVE-2026-71434","markdown":"https://insights.sbomify.com/CVE-2026-71434/index.md","name":"CVE-2026-71434","record":{"aliases":["GHSA-qhr7-v3xp-vw9m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"none","summary":"Unauthenticated attackers can upload disallowed file types via public frontend forms, bypassing administrator restrictions on file uploads.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.74.3 and 6.24.2, public frontend forms did not enforce the file upload restrictions that the Control Panel enforces, so an unauthenticated visitor could upload file types an administrator had intended to disallow through a form's assets or files field, and for assets fields, files could be stored on a public, web-accessible disk, though the application's global upload allowlist still blocked executable types such as .php and .html. This issue is fixed in versions 5.74.3 and 6.24.2.","ecosystems":["Packagist"],"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":"Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types","id":"CVE-2026-71434","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template","id":"CVE-2026-71435"},"packages":[{"ecosystem":"Packagist","fixed":["5.74.3"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-qhr7-v3xp-vw9m"},{"ecosystem":"Packagist","fixed":["5.74.3"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-qhr7-v3xp-vw9m"},{"ecosystem":"Packagist","fixed":["6.24.2"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-qhr7-v3xp-vw9m"},{"ecosystem":"Packagist","fixed":["6.24.2"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-qhr7-v3xp-vw9m"}],"prev":{"headline":"LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores","id":"CVE-2026-71433"},"products":["cms"],"published":"2026-08-06","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["statamic"]},"summary":"Unauthenticated attackers can upload disallowed file types via public frontend forms, bypassing administrator restrictions on file uploads.","url":"https://insights.sbomify.com/CVE-2026-71434/"}