{"answers":{"affected":"2 open source packages ship an affected version, including forkcms/forkcms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-1207 in the wild and no public exploit code.","fix":"Upgrade forkcms/forkcms to 3.2.5 or later.","what":"CVE-2012-1207 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-1207 and fix it if it is affected.\n\nWhat it is: CVE-2012-1207 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2012. 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-2012-1207 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- forkcms/forkcms (Packagist): affected all versions; fixed in 3.2.5\n- forkcms/forkcms (Packagist): affected all versions; fixed in 3.2.5\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-2012-1207/ (Markdown: https://insights.sbomify.com/CVE-2012-1207/index.md)","id":"CVE-2012-1207","markdown":"https://insights.sbomify.com/CVE-2012-1207/index.md","name":"CVE-2012-1207","record":{"aliases":["GHSA-4x28-j85r-668q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fork CMS","requires_auth":"none","summary":"Remote attackers can read arbitrary files via directory traversal in Fork CMS, potentially exposing sensitive system data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fork_cms","vendor":"fork-cms"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Directory traversal vulnerability in frontend/core/engine/javascript.php in Fork CMS 3.2.4 and possibly other versions before 3.2.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the module parameter to frontend/js.php.","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":"ForkCMS Directory Traversal vulnerability","id":"CVE-2012-1207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2012"},"n_packages":2,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2012-1208"},"packages":[{"ecosystem":"Packagist","fixed":["3.2.5"],"introduced":["0"],"last_affected":[],"package":"forkcms/forkcms","purl":null,"source":"GHSA-4x28-j85r-668q"},{"ecosystem":"Packagist","fixed":["3.2.5"],"introduced":["0"],"last_affected":[],"package":"forkcms/forkcms","purl":"pkg:composer/forkcms/forkcms","source":"GHSA-4x28-j85r-668q"}],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2012-1206"},"products":["n/a"],"published":"2012-02-20","related":[{"cvss_score":9.8,"headline":"Spoon Library as used in Fork CMS allows PHP object injection","id":"CVE-2019-15521","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":9.6,"headline":"SQL Injection in forkcms/forkcms","id":"CVE-2022-0153","kev_date_added":null,"published":"2022-03-24"},{"cvss_score":9,"headline":"SQL injection through marking blog comments on bulk as spam in forkcms/forkcms","id":"CVE-2022-1064","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":8.8,"headline":"Arbitrary file upload in Fork CMS","id":"CVE-2021-28931","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in forkcms","id":"CVE-2020-23264","kev_date_added":null,"published":"2021-05-06"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2020-24036","kev_date_added":null,"published":"2021-03-04"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in ForkCMS","id":"CVE-2020-23960","kev_date_added":null,"published":"2021-01-11"}],"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 read arbitrary files via directory traversal in Fork CMS, potentially exposing sensitive system data.","url":"https://insights.sbomify.com/CVE-2012-1207/"}