{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20253 exists.","fix":"No fix has been published for CVE-2017-20253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-20253 is a high-severity SQL injection vulnerability in Gegabyte My Projects, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-20253 and fix it if it is affected.\n\nWhat it is: CVE-2017-20253 is a high-severity SQL injection vulnerability in Gegabyte My Projects, published on 19 Jun 2026. 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-2017-20253 exists.\n\nAffected product: Gegabyte My Projects. 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-2017-20253/ (Markdown: https://insights.sbomify.com/CVE-2017-20253/index.md)","id":"CVE-2017-20253","markdown":"https://insights.sbomify.com/CVE-2017-20253/index.md","name":"CVE-2017-20253","record":{"aliases":["GHSA-8549-f9p2-9jv7"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Joomla component","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary SQL queries via the VerAyari parameter to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"my_projects","vendor":"gegabyte"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Joomla! Component My Projects 2.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the VerAyari parameter. Attackers can craft requests to the component endpoint with SQL injection payloads to extract sensitive database information including credentials and system data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Joomla! Component My Projects 2.0 SQL Injection","id":"CVE-2017-20253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Joomla! Component User Bench 1.0 SQL Injection via userid","id":"CVE-2017-20254"},"packages":[],"prev":{"headline":"Joomla NextGen Editor 2.1.0 SQL Injection via plname Parameter","id":"CVE-2017-20252"},"products":["My Projects"],"published":"2026-06-19","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["Gegabyte"]},"summary":"Unauthenticated attackers can execute arbitrary SQL queries via the VerAyari parameter to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2017-20253/"}