{"answers":{"affected":"2 open source packages ship an affected version, including statamic/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11422 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to 2.6.0 or later.","what":"CVE-2017-11422 is a high-severity missing authorization vulnerability in n/a, published on 24 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-11422 and fix it if it is affected.\n\nWhat it is: CVE-2017-11422 is a high-severity missing authorization vulnerability in n/a, published on 24 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-11422 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected all versions; fixed in 2.6.0\n- statamic/cms (Packagist): affected all versions; fixed in 2.6.0\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-2017-11422/ (Markdown: https://insights.sbomify.com/CVE-2017-11422/index.md)","id":"CVE-2017-11422","markdown":"https://insights.sbomify.com/CVE-2017-11422/index.md","name":"CVE-2017-11422","record":{"aliases":["GHSA-5m64-9hq5-5pf2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"low_privilege","summary":"Attackers can bypass permission checks to perform sensitive actions like resetting passwords or creating accounts in Statamic CMS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"statamic","vendor":"statamic"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Statamic framework before 2.6.0 does not correctly check a session's permissions when the methods from a user's class are called. Problematic methods include reset password, create new account, create new role, etc.","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 framework Incorrect Permission Assignment","id":"CVE-2017-11422","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-11423"},"packages":[{"ecosystem":"Packagist","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-5m64-9hq5-5pf2"},{"ecosystem":"Packagist","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-5m64-9hq5-5pf2"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2017-11421"},"products":["n/a"],"published":"2017-07-24","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.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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass permission checks to perform sensitive actions like resetting passwords or creating accounts in Statamic CMS.","url":"https://insights.sbomify.com/CVE-2017-11422/"}