{"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-4864 exists.","fix":"Upgrade froxlor/froxlor to 2.0.0-beta1 or later.","what":"CVE-2022-4864 is a medium-severity command injection vulnerability in froxlor/froxlor, published on 30 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4864 and fix it if it is affected.\n\nWhat it is: CVE-2022-4864 is a medium-severity command injection vulnerability in froxlor/froxlor, published on 30 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4864 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-4864/ (Markdown: https://insights.sbomify.com/CVE-2022-4864/index.md)","id":"CVE-2022-4864","markdown":"https://insights.sbomify.com/CVE-2022-4864/index.md","name":"CVE-2022-4864","record":{"aliases":["GHSA-3v7m-2jrh-vc93"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"none","summary":"Attackers can inject arguments to execute arbitrary commands in the Froxlor hosting panel, requiring an upgrade to secure the system.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"froxlor","vendor":"froxlor"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Argument Injection 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":"Argument Injection in froxlor/froxlor","id":"CVE-2022-4864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site Scripting (XSS) - Stored in usememos/memos","id":"CVE-2022-4865"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.0-beta1"],"introduced":["2.0.0-beta0"],"last_affected":[],"package":"froxlor/froxlor","purl":null,"source":"GHSA-3v7m-2jrh-vc93"},{"ecosystem":"Packagist","fixed":["2.0.0-beta1"],"introduced":["2.0.0-beta0"],"last_affected":[],"package":"froxlor/froxlor","purl":"pkg:composer/froxlor/froxlor","source":"GHSA-3v7m-2jrh-vc93"}],"prev":{"headline":"Improper Handling of Insufficient Permissions or Privileges in usememos/memos","id":"CVE-2022-4863"},"products":["froxlor/froxlor"],"published":"2022-12-30","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 inject arguments to execute arbitrary commands in the Froxlor hosting panel, requiring an upgrade to secure the system.","url":"https://insights.sbomify.com/CVE-2022-4864/"}