{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4428 exists.","fix":"No fix has been published for CVE-2006-4428 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4428 is a critical code injection vulnerability in n/a, published on 29 Aug 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-4428 and fix it if it is affected.\n\nWhat it is: CVE-2006-4428 is a critical code injection vulnerability in n/a, published on 29 Aug 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-4428 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-4428/ (Markdown: https://insights.sbomify.com/CVE-2006-4428/index.md)","id":"CVE-2006-4428","markdown":"https://insights.sbomify.com/CVE-2006-4428/index.md","name":"CVE-2006-4428","record":{"aliases":["GHSA-m8pg-mx2h-fq4v"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jupiter CMS","requires_auth":"none","summary":"Remote attackers could execute arbitrary PHP code via the template parameter in Jupiter CMS, though the vulnerability is disputed.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jupiter_cms","vendor":"jupiter_cms"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"PHP remote file inclusion vulnerability in index.php in Jupiter CMS 1.1.5 allows remote attackers to execute arbitrary PHP code via a URL in the template parameter.  NOTE: CVE disputes this claim, since the $template variable is defined as a static value before it is referenced in an include statement","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-08-26","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-08-26","kind":"exploitdb","ref":"28430","stars":null,"title":"Jupiter CMS 1.1.5 - 'index.php' Remote File Inclusion"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2006-4428","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2006-4429"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2006-4427"},"products":["n/a"],"published":"2006-08-29","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-0971","kev_date_added":null,"published":"2007-02-16"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2007-0972","kev_date_added":null,"published":"2007-02-16"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2007-0987","kev_date_added":null,"published":"2007-02-16"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-4876","kev_date_added":null,"published":"2006-09-19"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2007-0973","kev_date_added":null,"published":"2007-02-16"},{"cvss_score":5.1,"headline":"Code injection in n/a","id":"CVE-2007-0986","kev_date_added":null,"published":"2007-02-16"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-17","vendors":["n/a"]},"summary":"Remote attackers could execute arbitrary PHP code via the template parameter in Jupiter CMS, though the vulnerability is disputed.","url":"https://insights.sbomify.com/CVE-2006-4428/"}