{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-52745 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-52745 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-52745 is a medium-severity SQL injection vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-52745 and fix it if it is affected.\n\nWhat it is: CVE-2026-52745 is a medium-severity SQL injection vulnerability in 1Panel-dev CordysCRM, published on 18 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-52745 in the wild and no public exploit code.\n\nAffected product: 1Panel-dev CordysCRM. 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-2026-52745/ (Markdown: https://insights.sbomify.com/CVE-2026-52745/index.md)","id":"CVE-2026-52745","markdown":"https://insights.sbomify.com/CVE-2026-52745/index.md","name":"CVE-2026-52745","record":{"aliases":["GHSA-xrcr-hj37-q83j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"CordysCRM","requires_auth":"high_privilege","summary":"An authenticated user can exploit SQL injection in the customer pool sorting field to read sensitive data and cause service delays.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.0, the POST /account-pool/page endpoint allows an authenticated caller with MODULE_SETTING:UPDATE to place a crafted sort.name value into a dynamic SQL ORDER BY expression without strict server-side validation of the sorting field. The resulting time-based blind SQL injection can confirm database expression execution, infer database metadata and sensitive values, and introduce database delays that degrade service. This issue is fixed in version 1.7.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CordysCRM: Customer Public Pool Sorting Field SQL Injection","id":"CVE-2026-52745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"JSONata: Malicious inputs to \"$toMillis\" function can cause resource exhaustion","id":"CVE-2026-52746"},"packages":[],"prev":{"headline":"GoCD is vulnerable to authorization bypass via fetch artifact autosuggestion API","id":"CVE-2026-52744"},"products":["CordysCRM"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-19","vendors":["1Panel-dev"]},"summary":"An authenticated user can exploit SQL injection in the customer pool sorting field to read sensitive data and cause service delays.","url":"https://insights.sbomify.com/CVE-2026-52745/"}