{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5251 exists.","fix":"No fix has been published for CVE-2006-5251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5251 is a high-severity code injection vulnerability in n/a, published on 12 Oct 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-5251 and fix it if it is affected.\n\nWhat it is: CVE-2006-5251 is a high-severity code injection vulnerability in n/a, published on 12 Oct 2006. 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-2006-5251 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-2006-5251/ (Markdown: https://insights.sbomify.com/CVE-2006-5251/index.md)","id":"CVE-2006-5251","markdown":"https://insights.sbomify.com/CVE-2006-5251/index.md","name":"CVE-2006-5251","record":{"aliases":["GHSA-m6vv-f2fj-j4xc"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Deep CMS","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code in Deep CMS via a URL in the ConfigDir parameter.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"deep_cms","vendor":"deep_cms"}],"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 index.php in Deep CMS 2.0a allows remote attackers to execute arbitrary PHP code via a URL in the ConfigDir parameter.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-10-09","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-10-09","kind":"exploitdb","ref":"28773","stars":null,"title":"Deep CMS 2.0 - 'index.php' Remote File Inclusion"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2006-5251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2006-5252"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-5250"},"products":["n/a"],"published":"2006-10-12","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary PHP code in Deep CMS via a URL in the ConfigDir parameter.","url":"https://insights.sbomify.com/CVE-2006-5251/"}