{"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-2023-4304 in the wild and no public exploit code.","fix":"Upgrade froxlor/froxlor to 2.0.22 or later.","what":"CVE-2023-4304 is a low-severity vulnerability in froxlor/froxlor, published on 11 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4304 and fix it if it is affected.\n\nWhat it is: CVE-2023-4304 is a low-severity vulnerability in froxlor/froxlor, published on 11 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-4304 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- froxlor/froxlor (Packagist): affected all versions; fixed in 2.0.22\n- froxlor/froxlor (Packagist): affected all versions; fixed in 2.0.22\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-2023-4304/ (Markdown: https://insights.sbomify.com/CVE-2023-4304/index.md)","id":"CVE-2023-4304","markdown":"https://insights.sbomify.com/CVE-2023-4304/index.md","name":"CVE-2023-4304","record":{"aliases":["GHSA-9rmf-6qgj-g3wj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"high_privilege","summary":"Attackers can exploit business logic errors in Froxlor to bypass intended application workflows or restrictions.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"froxlor","vendor":"froxlor"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-840","name":null}],"description":"Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.22,2.1.0.","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":"Business Logic Errors in froxlor/froxlor","id":"CVE-2023-4304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Lock User Account \u003c= 1.0.3 - Arbitrary Account Lock/Unlock via CSRF","id":"CVE-2023-4307"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.22"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":null,"source":"GHSA-9rmf-6qgj-g3wj"},{"ecosystem":"Packagist","fixed":["2.0.22"],"introduced":["0"],"last_affected":[],"package":"froxlor/froxlor","purl":"pkg:composer/froxlor/froxlor","source":"GHSA-9rmf-6qgj-g3wj"}],"prev":{"headline":"HTML injection vulnerability in Fortify Plugin","id":"CVE-2023-4303"},"products":["froxlor/froxlor"],"published":"2023-08-11","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-04","vendors":["froxlor"]},"summary":"Attackers can exploit business logic errors in Froxlor to bypass intended application workflows or restrictions.","url":"https://insights.sbomify.com/CVE-2023-4304/"}