{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1677 exists.","fix":"No fix has been published for CVE-2009-1677 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-1677 is a medium-severity code injection vulnerability in n/a, published on 18 May 2009. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-1677 and fix it if it is affected.\n\nWhat it is: CVE-2009-1677 is a medium-severity code injection vulnerability in n/a, published on 18 May 2009. 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-2009-1677 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-2009-1677/ (Markdown: https://insights.sbomify.com/CVE-2009-1677/index.md)","id":"CVE-2009-1677","markdown":"https://insights.sbomify.com/CVE-2009-1677/index.md","name":"CVE-2009-1677","record":{"aliases":["GHSA-cj8c-64c6-4xr5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitweaver CMS","requires_auth":"low_privilege","summary":"Authenticated users or remote attackers can inject arbitrary PHP code into files via display name or Host header, leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitweaver","vendor":"bitweaver"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Multiple static code injection vulnerabilities in the saveFeed function in rss/feedcreator.class.php in Bitweaver 2.6 and earlier allow (1) remote authenticated users to inject arbitrary PHP code into files by placing PHP sequences into the account's \"display name\" setting and then invoking boards/boards_rss.php, and might allow (2) remote attackers to inject arbitrary PHP code into files via the HTTP Host header in a request to boards/boards_rss.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-05-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-05-12","kind":"exploitdb","ref":"8659","stars":null,"title":"Bitweaver 2.6 - 'saveFeed()' Remote Code Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2009-1677","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2009"},"n_packages":0,"n_references":5,"next":{"headline":"Path traversal in n/a","id":"CVE-2009-1678"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2009-1675"},"products":["n/a"],"published":"2009-05-18","related":[{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2009-1678","kev_date_added":null,"published":"2009-05-18"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-6375","kev_date_added":null,"published":"2007-12-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-6923","kev_date_added":null,"published":"2007-01-13"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4380","kev_date_added":null,"published":"2005-12-20"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2007-6412","kev_date_added":null,"published":"2007-12-17"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2006-6925","kev_date_added":null,"published":"2007-01-13"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Authenticated users or remote attackers can inject arbitrary PHP code into files via display name or Host header, leading to code execution.","url":"https://insights.sbomify.com/CVE-2009-1677/"}