{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0780 exists.","fix":"No fix has been published for CVE-2005-0780 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0780 is a medium-severity vulnerability in n/a, published on 20 Mar 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-0780 and fix it if it is affected.\n\nWhat it is: CVE-2005-0780 is a medium-severity vulnerability in n/a, published on 20 Mar 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-0780 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-0780/ (Markdown: https://insights.sbomify.com/CVE-2005-0780/index.md)","id":"CVE-2005-0780","markdown":"https://insights.sbomify.com/CVE-2005-0780/index.md","name":"CVE-2005-0780","record":{"aliases":["GHSA-9x3m-mrh3-f5j7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"paFileDB web application","requires_auth":"none","summary":"Remote attackers can obtain sensitive path information via direct requests to specific PHP scripts, exposing internal file system details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pafiledb","vendor":"php_arena"}],"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":"paFileDB 3.1 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) auth.php, (2) login.php, (3) category.php, (4) file.php, (5) team.php, (6) license.php, (7) custom.php, (8) admins.php, or (9) backupdb.php, which reveal the path in a PHP error message.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-12-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-12-04","kind":"exploitdb","ref":"24798","stars":null,"title":"PAFileDB 3.1 - Error Message Full Path Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2005-0780","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2005-0781"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2005-0779"},"products":["n/a"],"published":"2005-03-20","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-3808","kev_date_added":null,"published":"2007-07-17"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4329","kev_date_added":null,"published":"2005-12-17"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-2723","kev_date_added":null,"published":"2005-08-29"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-2000","kev_date_added":null,"published":"2005-06-20"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-0781","kev_date_added":null,"published":"2005-03-20"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2005-0327","kev_date_added":null,"published":"2005-02-10"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2005-2001","kev_date_added":null,"published":"2005-06-20"}],"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 obtain sensitive path information via direct requests to specific PHP scripts, exposing internal file system details.","url":"https://insights.sbomify.com/CVE-2005-0780/"}