{"answers":{"affected":"4 open source packages ship an affected version, including statamic/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33886 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to a fixed version for your release line: 5.73.16 or 6.7.2.","what":"CVE-2026-33886 is a medium-severity vulnerability in statamic cms, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33886 and fix it if it is affected.\n\nWhat it is: CVE-2026-33886 is a medium-severity vulnerability in statamic cms, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33886 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected from 5.73.12; fixed in 5.73.16\n- statamic/cms (Packagist): affected from 5.73.12; fixed in 5.73.16\n- statamic/cms (Packagist): affected from 6.5.0; fixed in 6.7.2\n- statamic/cms (Packagist): affected from 6.5.0; fixed in 6.7.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-33886/ (Markdown: https://insights.sbomify.com/CVE-2026-33886/index.md)","id":"CVE-2026-33886","markdown":"https://insights.sbomify.com/CVE-2026-33886/index.md","name":"CVE-2026-33886","record":{"aliases":["GHSA-gcqf-5x9f-hq7f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"low_privilege","summary":"Content editors can access sensitive application configuration values by inserting config variables into Antlers-enabled fields.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"statamic","vendor":"statamic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Statamic is a Laravel and Git powered content management system (CMS). Starting in version 5.7.12 and prior to versions 5.73.16 and 6.7.2, a control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content. This has been fixed in 5.73.16 and 6.7.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's sensitive configuration values are exposed to content editors via Antlers-enabled fields","id":"CVE-2026-33886","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Statamic allows unauthorized content access through missing authorization in its revision controllers","id":"CVE-2026-33887"},"packages":[{"ecosystem":"Packagist","fixed":["5.73.16"],"introduced":["5.73.12"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-gcqf-5x9f-hq7f"},{"ecosystem":"Packagist","fixed":["5.73.16"],"introduced":["5.73.12"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-gcqf-5x9f-hq7f"},{"ecosystem":"Packagist","fixed":["6.7.2"],"introduced":["6.5.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-gcqf-5x9f-hq7f"},{"ecosystem":"Packagist","fixed":["6.7.2"],"introduced":["6.5.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-gcqf-5x9f-hq7f"}],"prev":{"headline":"Statamic has an Open Redirect on unauthenticated endpoints via URL parsing differential","id":"CVE-2026-33885"},"products":["cms"],"published":"2026-03-27","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-45364","kev_date_added":null,"published":"2022-02-10"},{"cvss_score":9.3,"headline":"Statamic is vulnerable to account takeover via password reset link injection","id":"CVE-2026-27593","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":8.8,"headline":"Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass","id":"CVE-2026-27939","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":8.8,"headline":"Remote code execution via form uploads in statamic/cms","id":"CVE-2023-48217","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":8.8,"headline":"Statamic framework Incorrect Permission Assignment","id":"CVE-2017-11422","kev_date_added":null,"published":"2017-07-24"},{"cvss_score":8.7,"headline":"Statamic has Stored XSS via SVG Sanitization Bypass","id":"CVE-2026-33172","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.7,"headline":"Statamic vulnerable to privilege escalation via stored cross-site scripting","id":"CVE-2026-28426","kev_date_added":null,"published":"2026-02-27"}],"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-03-31","vendors":["statamic"]},"summary":"Content editors can access sensitive application configuration values by inserting config variables into Antlers-enabled fields.","url":"https://insights.sbomify.com/CVE-2026-33886/"}