{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-2859 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-2859 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-2859 is a high-severity code injection vulnerability in n/a, published on 6 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-2859 and fix it if it is affected.\n\nWhat it is: CVE-2006-2859 is a high-severity code injection vulnerability in n/a, published on 6 Jun 2006. 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-2006-2859 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-2006-2859/ (Markdown: https://insights.sbomify.com/CVE-2006-2859/index.md)","id":"CVE-2006-2859","markdown":"https://insights.sbomify.com/CVE-2006-2859/index.md","name":"CVE-2006-2859","record":{"aliases":["GHSA-v287-828q-jwgf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MyBloggie web application","requires_auth":"none","summary":"Remote attackers could execute arbitrary PHP code via URL parameters, though the vulnerability is disputed and may not exist in the core code.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mybloggie","vendor":"mywebland"}],"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":"PHP remote file inclusion vulnerability in MyBloggie 2.1.1 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the mybloggie_root_path parameter to (1) admin.php or (2) scode.php. NOTE: this issue has been disputed in multiple third party followups, which say that the MyBloggie source code does not demonstrate the issue, so it might be the result of another module.  CVE analysis as of 20060605 agrees with the dispute.  In addition, scode.php is not part of the MyBloggie distribution","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":"Code injection in n/a","id":"CVE-2006-2859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Code injection in n/a","id":"CVE-2006-2860"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-2858"},"products":["n/a"],"published":"2006-06-06","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2007-3194","kev_date_added":null,"published":"2007-06-12"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-3003","kev_date_added":null,"published":"2007-06-04"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-4042","kev_date_added":null,"published":"2006-08-09"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-3905","kev_date_added":null,"published":"2006-07-27"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4225","kev_date_added":null,"published":"2005-12-14"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3153","kev_date_added":null,"published":"2005-10-05"}],"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 could execute arbitrary PHP code via URL parameters, though the vulnerability is disputed and may not exist in the core code.","url":"https://insights.sbomify.com/CVE-2006-2859/"}