{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76899 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-76899 and fix it if it is affected.\n\nWhat it is: CVE-2026-76899 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-76899 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-76899/ (Markdown: https://insights.sbomify.com/CVE-2026-76899/index.md)","id":"CVE-2026-76899","markdown":"https://insights.sbomify.com/CVE-2026-76899/index.md","name":"CVE-2026-76899","record":{"aliases":["GHSA-x6p7-vhgp-6r3q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CordysCRM","requires_auth":"high_privilege","summary":"Authenticated attackers can execute SQL queries via the sort parameter to read database values in CordysCRM.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/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"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. From 1.7.0 until 1.7.4, POST /account-pool/page allows an authenticated caller with MODULE_SETTING_UPDATE to place an arbitrary database function in SortRequest.name because CustomerPoolController.page omits Spring request validation, SortRequest.getName relies on an incomplete blacklist, and the CommonMapper.xml sort fragment inserts ${sortName} into an ORDER BY clause. Functions such as extractvalue and updatexml bypass the blacklist and can expose database values through an error oracle when the query returns at least one row. This issue is fixed in version 1.7.4.","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: Authenticated SQL injection via `sort.name` on `POST /account-pool/page`","id":"CVE-2026-76899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"CordysCRM: SSRF via Approval Flow Webhook Execution due to Missing SSRF Validation at Runtime","id":"CVE-2026-76900"},"packages":[],"prev":{"headline":"draw.io: Unauthenticated SSRF via IPv6 ULA blocklist bypass in /embed2.js","id":"CVE-2026-76898"},"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-24","vendors":["1Panel-dev"]},"summary":"Authenticated attackers can execute SQL queries via the sort parameter to read database values in CordysCRM.","url":"https://insights.sbomify.com/CVE-2026-76899/"}