{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2075 exists.","fix":"No fix has been published for CVE-2005-2075 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2075 is a medium-severity vulnerability in n/a, published on 29 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2075 and fix it if it is affected.\n\nWhat it is: CVE-2005-2075 is a medium-severity vulnerability in n/a, published on 29 Jun 2005. 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-2005-2075 exists.\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-2005-2075/ (Markdown: https://insights.sbomify.com/CVE-2005-2075/index.md)","id":"CVE-2005-2075","markdown":"https://insights.sbomify.com/CVE-2005-2075/index.md","name":"CVE-2005-2075","record":{"aliases":["GHSA-m42v-gfgm-p359"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP-Fusion CMS","requires_auth":"none","summary":"Remote attackers can access sensitive database backups via predictable filenames in the web root, exposing confidential data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"php_fusion","vendor":"php_fusion"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"PHP-Fusion 5.0 and 6.0 stores the database file with a predictable filename under the web document root with insufficient access control, which allows remote attackers to obtain sensitive information via a direct request to the filename in the administration/db_backups directory in PHP-Fusion 6.0 or the fusion_admin/db_backups directory in 5.0.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-06-25","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-06-25","kind":"exploitdb","ref":"1068","stars":null,"title":"PHP-Fusion 6.00.105 - Accessible Database Backups Download"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2005-2075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-2076"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-2074"},"products":["n/a"],"published":"2005-06-29","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4517","kev_date_added":null,"published":"2005-12-28"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4005","kev_date_added":null,"published":"2005-12-05"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3740","kev_date_added":null,"published":"2005-11-22"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3157","kev_date_added":null,"published":"2005-10-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3158","kev_date_added":null,"published":"2005-10-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3160","kev_date_added":null,"published":"2005-10-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3161","kev_date_added":null,"published":"2005-10-06"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can access sensitive database backups via predictable filenames in the web root, exposing confidential data.","url":"https://insights.sbomify.com/CVE-2005-2075/"}