{"answers":{"affected":"2 open source packages ship an affected version, including october/october. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16244 in the wild and no public exploit code.","fix":"Upgrade october/october to 1.0.427 or later.","what":"CVE-2017-16244 is a high-severity vulnerability in Octobercms October, published on 1 Nov 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-2017-16244 and fix it if it is affected.\n\nWhat it is: CVE-2017-16244 is a high-severity vulnerability in Octobercms October, published on 1 Nov 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-2017-16244 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- october/october (Packagist): affected all versions; fixed in 1.0.427\n- october/october (Packagist): affected all versions; fixed in 1.0.427\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-16244/ (Markdown: https://insights.sbomify.com/CVE-2017-16244/index.md)","id":"CVE-2017-16244","markdown":"https://insights.sbomify.com/CVE-2017-16244/index.md","name":"CVE-2017-16244","record":{"aliases":["GHSA-vm6r-4p4v-232x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"OctoberCMS","requires_auth":"none","summary":"An attacker can take over a victim's account in OctoberCMS by bypassing CSRF protections via a specific postback variable.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"october","vendor":"octobercms"}],"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":"Cross-Site Request Forgery exists in OctoberCMS 1.0.426 (aka Build 426) due to improper validation of CSRF tokens for postback handling, allowing an attacker to successfully take over the victim's account. The attack bypasses a protection mechanism involving X-CSRF headers and CSRF tokens via a certain _handler postback variable.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2017-11-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-11-01","kind":"exploitdb","ref":"43106","stars":null,"title":"OctoberCMS 1.0.426 (Build 426) - Cross-Site Request Forgery"}],"tier":"poc_unverified"},"has_fix":true,"headline":"October CMS CSRF","id":"CVE-2017-16244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"octobercms:october","products":["octobercms:october"],"type":"csrf","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2017-16248"},"packages":[{"ecosystem":"Packagist","fixed":["1.0.427"],"introduced":["0"],"last_affected":[],"package":"october/october","purl":null,"source":"GHSA-vm6r-4p4v-232x"},{"ecosystem":"Packagist","fixed":["1.0.427"],"introduced":["0"],"last_affected":[],"package":"october/october","purl":"pkg:composer/october/october","source":"GHSA-vm6r-4p4v-232x"}],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-16242"},"products":["n/a"],"published":"2017-11-01","related":[{"cvss_score":8.2,"headline":"October CMS Improper Authentication","id":"CVE-2021-32648","kev_date_added":"2022-01-18","published":"2021-08-26"},{"cvss_score":9.8,"headline":"October CMS Session ID not invalidated after logout","id":"CVE-2021-3311","kev_date_added":null,"published":"2021-02-05"},{"cvss_score":9.8,"headline":"October CMS File Upload Vulnerability","id":"CVE-2017-1000194","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2017-1000196","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2017-1000197","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.1,"headline":"October CMS safe mode bypass using Twig sandbox escape","id":"CVE-2023-44382","kev_date_added":null,"published":"2023-12-01"},{"cvss_score":8.8,"headline":"Authenticated file write leads to remote code execution in october/system","id":"CVE-2021-32649","kev_date_added":null,"published":"2022-01-14"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can take over a victim's account in OctoberCMS by bypassing CSRF protections via a specific postback variable.","url":"https://insights.sbomify.com/CVE-2017-16244/"}