{"answers":{"affected":"4 open source packages ship an affected version, including in2code/lux. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35628 in the wild and no public exploit code.","fix":"Upgrade in2code/lux to a fixed version for your release line: 17.6.1 or 24.0.2.","what":"CVE-2022-35628 is a critical SQL injection vulnerability in n/a, published on 12 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-35628 and fix it if it is affected.\n\nWhat it is: CVE-2022-35628 is a critical SQL injection vulnerability in n/a, published on 12 Jul 2022. 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-2022-35628 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- in2code/lux (Packagist): affected all versions; fixed in 17.6.1\n- in2code/lux (Packagist): affected all versions; fixed in 17.6.1\n- in2code/lux (Packagist): affected from 18.0.0; fixed in 24.0.2\n- in2code/lux (Packagist): affected from 18.0.0; fixed in 24.0.2\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-2022-35628/ (Markdown: https://insights.sbomify.com/CVE-2022-35628/index.md)","id":"CVE-2022-35628","markdown":"https://insights.sbomify.com/CVE-2022-35628/index.md","name":"CVE-2022-35628","record":{"aliases":["GHSA-rpxg-hg79-h8q9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 lux extension","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the lux extension in TYPO3, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"living_user_experience","vendor":"in2code"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection issue was discovered in the lux extension before 17.6.1, and 18.x through 24.x before 24.0.2, for TYPO3.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SQL Injection in typo3 extension \"LUX - TYPO3 Marketing Automation\"","id":"CVE-2022-35628","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":4,"n_references":1,"next":{"headline":"Velociraptor Client ID Spoofing","id":"CVE-2022-35629"},"packages":[{"ecosystem":"Packagist","fixed":["17.6.1"],"introduced":["0"],"last_affected":[],"package":"in2code/lux","purl":null,"source":"GHSA-rpxg-hg79-h8q9"},{"ecosystem":"Packagist","fixed":["17.6.1"],"introduced":["0"],"last_affected":[],"package":"in2code/lux","purl":"pkg:composer/in2code/lux","source":"GHSA-rpxg-hg79-h8q9"},{"ecosystem":"Packagist","fixed":["24.0.2"],"introduced":["18.0.0"],"last_affected":[],"package":"in2code/lux","purl":null,"source":"GHSA-rpxg-hg79-h8q9"},{"ecosystem":"Packagist","fixed":["24.0.2"],"introduced":["18.0.0"],"last_affected":[],"package":"in2code/lux","purl":"pkg:composer/in2code/lux","source":"GHSA-rpxg-hg79-h8q9"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-35624"},"products":["n/a"],"published":"2022-07-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the lux extension in TYPO3, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2022-35628/"}