{"answers":{"affected":"2 open source packages ship an affected version, including froxlor/froxlor. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4867 exists.","fix":"Upgrade froxlor/froxlor to 2.0.0-beta1 or later.","what":"CVE-2022-4867 is a low-severity vulnerability in froxlor/froxlor, published on 31 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-4867 and fix it if it is affected.\n\nWhat it is: CVE-2022-4867 is a low-severity vulnerability in froxlor/froxlor, published on 31 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4867 exists.\n\nAffected packages and fixed versions:\n- froxlor/froxlor (Packagist): affected from 2.0.0-beta0; fixed in 2.0.0-beta1\n- froxlor/froxlor (Packagist): affected from 2.0.0-beta0; fixed in 2.0.0-beta1\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-2022-4867/ (Markdown: https://insights.sbomify.com/CVE-2022-4867/index.md)","id":"CVE-2022-4867","markdown":"https://insights.sbomify.com/CVE-2022-4867/index.md","name":"CVE-2022-4867","record":{"aliases":["GHSA-6gwx-gw56-qhf7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"low_privilege","summary":"Attackers can trick authenticated users into performing unwanted actions in the Froxlor hosting panel via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"froxlor","vendor":"froxlor"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Cross-Site Request Forgery (CSRF) in froxlor/froxlor","id":"CVE-2022-4867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Improper Authorization in froxlor/froxlor","id":"CVE-2022-4868"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.0-beta1"],"introduced":["2.0.0-beta0"],"last_affected":[],"package":"froxlor/froxlor","purl":null,"source":"GHSA-6gwx-gw56-qhf7"},{"ecosystem":"Packagist","fixed":["2.0.0-beta1"],"introduced":["2.0.0-beta0"],"last_affected":[],"package":"froxlor/froxlor","purl":"pkg:composer/froxlor/froxlor","source":"GHSA-6gwx-gw56-qhf7"}],"prev":{"headline":"Cross-site Scripting (XSS) - Stored in usememos/memos","id":"CVE-2022-4866"},"products":["froxlor/froxlor"],"published":"2022-12-31","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["froxlor"]},"summary":"Attackers can trick authenticated users into performing unwanted actions in the Froxlor hosting panel via CSRF.","url":"https://insights.sbomify.com/CVE-2022-4867/"}