{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2699 is a medium-severity vulnerability in n/a, published on 25 Aug 2005. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2699 and fix it if it is affected.\n\nWhat it is: CVE-2005-2699 is a medium-severity vulnerability in n/a, published on 25 Aug 2005. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-2699 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-2699/ (Markdown: https://insights.sbomify.com/CVE-2005-2699/index.md)","id":"CVE-2005-2699","markdown":"https://insights.sbomify.com/CVE-2005-2699/index.md","name":"CVE-2005-2699","record":{"aliases":["GHSA-h455-x6w8-x79r"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHPKit CMS","requires_auth":"high_privilege","summary":"Authenticated administrators can upload malicious PHP files to execute arbitrary code, though this may not cross privilege boundaries if admin access is already required.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpkit","vendor":"phpkit"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unrestricted file upload vulnerability in admin/admin.php in PHPKit 1.6.1 allows remote authenticated administrators to execute arbitrary PHP code by uploading a .php file to the content/images/ directory using images.php.  NOTE: if a PHPKit administrator must already have access to the end system to install or modify configuration of the product, then this issue might not cross privilege boundaries, and should not be included in CVE.","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":"File upload in n/a","id":"CVE-2005-2699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2005"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2005-2700"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-2698"},"products":["n/a"],"published":"2005-08-25","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2016-10758","kev_date_added":null,"published":"2019-05-24"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-6134","kev_date_added":null,"published":"2007-11-27"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-7115","kev_date_added":null,"published":"2007-03-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-0179","kev_date_added":null,"published":"2007-01-11"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3553","kev_date_added":null,"published":"2005-11-16"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-2683","kev_date_added":null,"published":"2005-08-23"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2004-1538","kev_date_added":null,"published":"2005-02-19"}],"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":"Authenticated administrators can upload malicious PHP files to execute arbitrary code, though this may not cross privilege boundaries if admin access is already required.","url":"https://insights.sbomify.com/CVE-2005-2699/"}