{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35811 exists.","fix":"No fix has been published for CVE-2023-35811 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-35811 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 17 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-35811 and fix it if it is affected.\n\nWhat it is: CVE-2023-35811 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 17 Jun 2023. 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-2023-35811 exists.\n\nAffected product: Sugarcrm Sugarcrm. 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-2023-35811/ (Markdown: https://insights.sbomify.com/CVE-2023-35811/index.md)","id":"CVE-2023-35811","markdown":"https://insights.sbomify.com/CVE-2023-35811/index.md","name":"CVE-2023-35811","record":{"aliases":["GHSA-hxx9-xh5r-fc5x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SugarCRM Enterprise","requires_auth":"low_privilege","summary":"Attackers with regular user privileges can inject SQL code via the REST API due to missing input validation, potentially reading or modifying data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sugarcrm","vendor":"sugarcrm"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"An issue was discovered in SugarCRM Enterprise before 11.0.6 and 12.x before 12.0.3. Two SQL Injection vectors have been identified in the REST API. By using crafted requests, custom SQL code can be injected through the REST API because of missing input validation. Regular user privileges can use used for exploitation. Editions other than Enterprise are also affected.","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":"SQL injection in n/a","id":"CVE-2023-35811","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sugarcrm:sugarcrm","products":["sugarcrm:sugarcrm"],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2023-35812"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2023-35810"},"products":["n/a"],"published":"2023-06-17","related":[{"cvss_score":8.8,"headline":"Multiple SugarCRM Products Remote Code Execution","id":"CVE-2023-22952","kev_date_added":"2023-02-02","published":"2023-01-11"},{"cvss_score":10,"headline":"SQL injection in n/a","id":"CVE-2004-1225","kev_date_added":null,"published":"2004-12-15"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-7472","kev_date_added":null,"published":"2020-11-12"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2012-0694","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2014-3244","kev_date_added":null,"published":"2018-02-01"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-6308","kev_date_added":null,"published":"2018-01-25"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2023-46815","kev_date_added":null,"published":"2023-10-27"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-17","vendors":["n/a"]},"summary":"Attackers with regular user privileges can inject SQL code via the REST API due to missing input validation, potentially reading or modifying data.","url":"https://insights.sbomify.com/CVE-2023-35811/"}