{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2400 is a high-severity authentication bypass vulnerability in n/a, published on 27 Jul 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-2400 and fix it if it is affected.\n\nWhat it is: CVE-2005-2400 is a high-severity authentication bypass vulnerability in n/a, published on 27 Jul 2005. 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-2005-2400 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-2005-2400/ (Markdown: https://insights.sbomify.com/CVE-2005-2400/index.md)","id":"CVE-2005-2400","markdown":"https://insights.sbomify.com/CVE-2005-2400/index.md","name":"CVE-2005-2400","record":{"aliases":["GHSA-36cj-4hv4-3cpw"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PHPFinance application","requires_auth":"none","summary":"Remote attackers can bypass login in PHPFinance to gain unauthorized privileges.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpfinance","vendor":"phpfinance"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The inc.login.php scripts in PHPFinance 0.3 allows remote attackers to bypass the login and gain privileges.","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":"Auth bypass in n/a","id":"CVE-2005-2400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2005"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-2401"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-2399"},"products":["n/a"],"published":"2005-07-27","related":[],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can bypass login in PHPFinance to gain unauthorized privileges.","url":"https://insights.sbomify.com/CVE-2005-2400/"}