{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3158 exists.","fix":"No fix has been published for CVE-2006-3158 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3158 is a high-severity vulnerability in n/a, published on 22 Jun 2006. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-3158 and fix it if it is affected.\n\nWhat it is: CVE-2006-3158 is a high-severity vulnerability in n/a, published on 22 Jun 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3158 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-3158/ (Markdown: https://insights.sbomify.com/CVE-2006-3158/index.md)","id":"CVE-2006-3158","markdown":"https://insights.sbomify.com/CVE-2006-3158/index.md","name":"CVE-2006-3158","record":{"aliases":["GHSA-4mh4-7x7g-rjj8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Eduha Meeting","requires_auth":"low_privilege","summary":"Remote attackers can upload and execute arbitrary PHP code in Eduha Meeting by bypassing file extension restrictions during the add action.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"eduha_meeting","vendor":"eduha_meeting"}],"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":"index.php in Eduha Meeting does not properly restrict file extensions before permitting a file upload, which allows remote attackers to bypass security checks and upload or execute arbitrary php code via the add action.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-06-19","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-06-19","kind":"exploitdb","ref":"28058","stars":null,"title":"Eduha Meeting - 'index.php' Arbitrary File Upload"}],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2006-3158","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Path traversal in n/a","id":"CVE-2006-3159"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-3157"},"products":["n/a"],"published":"2006-06-22","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-08-07","vendors":["n/a"]},"summary":"Remote attackers can upload and execute arbitrary PHP code in Eduha Meeting by bypassing file extension restrictions during the add action.","url":"https://insights.sbomify.com/CVE-2006-3158/"}