{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45364 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45364 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45364 is a critical code injection vulnerability in n/a, published on 10 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-45364 and fix it if it is affected.\n\nWhat it is: CVE-2021-45364 is a critical code injection vulnerability in n/a, published on 10 Feb 2022. 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-2021-45364 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2021-45364/ (Markdown: https://insights.sbomify.com/CVE-2021-45364/index.md)","id":"CVE-2021-45364","markdown":"https://insights.sbomify.com/CVE-2021-45364/index.md","name":"CVE-2021-45364","record":{"aliases":["GHSA-hv3v-c734-65qr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"none","summary":"A code execution vulnerability was reported in Statamic, though the vendor states the affected code was not used in any product.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"statamic","vendor":"statamic"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A Code Execution vulnerability exists in Statamic Version through 3.2.26 via SettingsController.php. NOTE: the vendor indicates that there was an error in publishing this CVE Record, and that all parties agree that the affected code was not used in any Statamic product","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2021-45364","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2021-45379"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-45357"},"products":["n/a"],"published":"2022-02-10","related":[{"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A code execution vulnerability was reported in Statamic, though the vendor states the affected code was not used in any product.","url":"https://insights.sbomify.com/CVE-2021-45364/"}