{"answers":{"affected":"2 open source packages ship an affected version, including froxlor/froxlor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12642 in the wild and no public exploit code.","fix":"Upgrade froxlor/froxlor to 0.9.40 or later.","what":"CVE-2018-12642 is a high-severity missing authorization vulnerability in n/a, published on 22 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12642 and fix it if it is affected.\n\nWhat it is: CVE-2018-12642 is a high-severity missing authorization vulnerability in n/a, published on 22 Jun 2018. 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-2018-12642 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- froxlor/froxlor (Packagist): affected all versions; fixed in 0.9.40\n- froxlor/froxlor (Packagist): affected all versions; fixed in 0.9.40\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-2018-12642/ (Markdown: https://insights.sbomify.com/CVE-2018-12642/index.md)","id":"CVE-2018-12642","markdown":"https://insights.sbomify.com/CVE-2018-12642/index.md","name":"CVE-2018-12642","record":{"aliases":["GHSA-r6g8-mq9v-cgp4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"none","summary":"Attackers can access or modify support tickets belonging to other users due to incorrect access control checks in Froxlor.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"froxlor","vendor":"froxlor"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.","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":"Froxlor Incorrect Access Control","id":"CVE-2018-12642","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-12648"},"packages":[{"ecosystem":"Packagist","fixed":["0.9.40"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":null,"source":"GHSA-r6g8-mq9v-cgp4"},{"ecosystem":"Packagist","fixed":["0.9.40"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":"pkg:composer/froxlor/froxlor","source":"GHSA-r6g8-mq9v-cgp4"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-12641"},"products":["n/a"],"published":"2018-06-22","related":[{"cvss_score":10,"headline":"Froxlor has Local File Inclusion via path traversal in API `def_language` parameter that leads to Remote Code Execution","id":"CVE-2026-41228","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":9.9,"headline":"Improper Link Resolution Before File Access in froxlor/froxlor","id":"CVE-2023-6069","kev_date_added":null,"published":"2023-11-10"},{"cvss_score":9.9,"headline":"Code Injection in froxlor/froxlor","id":"CVE-2023-0671","kev_date_added":null,"published":"2023-02-04"},{"cvss_score":9.8,"headline":"Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor","id":"CVE-2023-3173","kev_date_added":null,"published":"2023-06-09"},{"cvss_score":9.8,"headline":"Authentication Bypass by Primary Weakness in froxlor/froxlor","id":"CVE-2023-1307","kev_date_added":null,"published":"2023-03-10"},{"cvss_score":9.8,"headline":"Froxlor SQL injection vulnerability","id":"CVE-2021-42325","kev_date_added":null,"published":"2021-10-12"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2015-5959","kev_date_added":null,"published":"2017-09-06"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can access or modify support tickets belonging to other users due to incorrect access control checks in Froxlor.","url":"https://insights.sbomify.com/CVE-2018-12642/"}