{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0219 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 16 Jan 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-0219 and fix it if it is affected.\n\nWhat it is: CVE-2006-0219 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 16 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-0219 in the wild and no public exploit code.\n\nAffected product: Mybulletinboard Mybulletinboard. 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-0219/ (Markdown: https://insights.sbomify.com/CVE-2006-0219/index.md)","id":"CVE-2006-0219","markdown":"https://insights.sbomify.com/CVE-2006-0219/index.md","name":"CVE-2006-0219","record":{"aliases":["GHSA-fh38-h389-fqw2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MyBB forum software","requires_auth":"low_privilege","summary":"Attackers can execute SQL injection via attachment names in MyBB due to missing security patches in the update distribution.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mybulletinboard","vendor":"mybulletinboard"}],"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":"The original distribution of MyBulletinBoard (MyBB) to update from older versions to 1.0.2 omits or includes older versions of certain critical files, which allows attackers to conduct (1) SQL injection attacks via an attachment name that is not properly handled by inc/functions_upload.php (CVE-2005-4602), and possibly (2) other attacks related to threadmode in usercp.php.","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":"SQL injection in n/a","id":"CVE-2006-0219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mybulletinboard:mybulletinboard","products":["mybulletinboard:mybulletinboard"],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0220"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-0218"},"products":["n/a"],"published":"2006-01-16","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2005-4200","kev_date_added":null,"published":"2005-12-13"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2009-2230","kev_date_added":null,"published":"2009-06-26"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2008-0382","kev_date_added":null,"published":"2008-01-22"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-2211","kev_date_added":null,"published":"2007-04-24"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-3758","kev_date_added":null,"published":"2006-07-21"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-3760","kev_date_added":null,"published":"2006-07-21"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-3775","kev_date_added":null,"published":"2006-07-21"}],"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":"Attackers can execute SQL injection via attachment names in MyBB due to missing security patches in the update distribution.","url":"https://insights.sbomify.com/CVE-2006-0219/"}