{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-5959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-5959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-5959 is a critical vulnerability in n/a, published on 6 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-5959 and fix it if it is affected.\n\nWhat it is: CVE-2015-5959 is a critical vulnerability in n/a, published on 6 Sep 2017. 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-2015-5959 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2015-5959/ (Markdown: https://insights.sbomify.com/CVE-2015-5959/index.md)","id":"CVE-2015-5959","markdown":"https://insights.sbomify.com/CVE-2015-5959/index.md","name":"CVE-2015-5959","record":{"aliases":["GHSA-3f2c-xwqh-4w82"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Froxlor hosting panel","requires_auth":"none","summary":"Remote attackers can read the database password from log files in Froxlor, potentially compromising the backend database.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"froxlor","vendor":"froxlor"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Froxlor before 0.9.33.2 with the default configuration/setup might allow remote attackers to obtain the database password by reading /logs/sql-error.log.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2015-5959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2015-5960"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2015-5958"},"products":["n/a"],"published":"2017-09-06","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"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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 the database password from log files in Froxlor, potentially compromising the backend database.","url":"https://insights.sbomify.com/CVE-2015-5959/"}