{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6030 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6030 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6030 is a high-severity SQL injection vulnerability in n/a, published on 21 Nov 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-6030 and fix it if it is affected.\n\nWhat it is: CVE-2006-6030 is a high-severity SQL injection vulnerability in n/a, published on 21 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-6030 in the wild and no public exploit code.\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-6030/ (Markdown: https://insights.sbomify.com/CVE-2006-6030/index.md)","id":"CVE-2006-6030","markdown":"https://insights.sbomify.com/CVE-2006-6030/index.md","name":"CVE-2006-6030","record":{"aliases":["GHSA-crh3-8h4m-5j8m"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"E-Calendar Pro","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands via injection in login or search fields, potentially compromising calendar data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"e-calendar_pro","vendor":"futuretec"}],"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":"Multiple SQL injection vulnerabilities in E-Calendar Pro 3.0 allow remote attackers to execute arbitrary SQL commands via the (1) username and (2) passwd (Password) fields in (a) admin/default.asp; or the (3) Event Title, (4) Location, or (5) Description field when making a search engine query in (b) search.asp.  NOTE: some of these details are obtained from third party information.","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-6030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"SQL injection in n/a","id":"CVE-2006-6031"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-6029"},"products":["n/a"],"published":"2006-11-21","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via injection in login or search fields, potentially compromising calendar data.","url":"https://insights.sbomify.com/CVE-2006-6030/"}