{"answers":{"affected":"2 open source packages ship an affected version, including Umbraco.CMS. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-8814 in the wild and no public exploit code.","fix":"Upgrade Umbraco.CMS to 7.4.0 or later.","what":"CVE-2015-8814 is a high-severity vulnerability in n/a, published on 3 Mar 2017. 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-2015-8814 and fix it if it is affected.\n\nWhat it is: CVE-2015-8814 is a high-severity vulnerability in n/a, published on 3 Mar 2017. 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-2015-8814 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Umbraco.CMS (NuGet): affected all versions; fixed in 7.4.0\n- Umbraco.CMS (NuGet): affected all versions; fixed in 7.4.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-2015-8814/ (Markdown: https://insights.sbomify.com/CVE-2015-8814/index.md)","id":"CVE-2015-8814","markdown":"https://insights.sbomify.com/CVE-2015-8814/index.md","name":"CVE-2015-8814","record":{"aliases":["GHSA-5f6p-4hxq-rjxm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Umbraco CMS","requires_auth":"none","summary":"Remote attackers can bypass anti-forgery measures to perform CSRF attacks, potentially modifying user account information in Umbraco CMS.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"umbraco","vendor":"umbraco"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Umbraco before 7.4.0 allows remote attackers to bypass anti-forgery security measures and conduct cross-site request forgery (CSRF) attacks as demonstrated by editing user account information in the templates.asmx.cs file.","ecosystems":["NuGet"],"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":"Umbraco CMS vulnerable to CSRF","id":"CVE-2015-8814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"csrf","year":"2015"},"n_packages":2,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-8815"},"packages":[{"ecosystem":"NuGet","fixed":["7.4.0"],"introduced":["0"],"last_affected":[],"package":"Umbraco.CMS","purl":null,"source":"GHSA-5f6p-4hxq-rjxm"},{"ecosystem":"NuGet","fixed":["7.4.0"],"introduced":["0"],"last_affected":[],"package":"Umbraco.CMS","purl":"pkg:nuget/Umbraco.CMS","source":"GHSA-5f6p-4hxq-rjxm"}],"prev":{"headline":"Umbraco CMS vulnerable to CSRF","id":"CVE-2015-8813"},"products":["n/a"],"published":"2017-03-03","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13957","kev_date_added":null,"published":"2019-10-02"},{"cvss_score":8.2,"headline":"Umbraco CMS vulnerable to CSRF","id":"CVE-2015-8813","kev_date_added":null,"published":"2017-03-03"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2015-8815","kev_date_added":null,"published":"2017-03-03"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can bypass anti-forgery measures to perform CSRF attacks, potentially modifying user account information in Umbraco CMS.","url":"https://insights.sbomify.com/CVE-2015-8814/"}