CVE-2026-76899 json
CordysCRM: Authenticated SQL injection via `sort.name` on `POST /account-pool/page`
published 2026-09-18 51 d ago modified 2026-09-24 45 d ago also EUVD-2026-83373
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L |
Affected products
- 1Panel-dev CordysCRM
Classification
References
- github.com /1Panel-dev/CordysCRM/pull/2975
- github.com /1Panel-dev/CordysCRM/commit/3e6a7003ac5c94bc1166c6065e64420be2f188a8
- github.com /1Panel-dev/CordysCRM/commit/b217166af2935c827c8d73bf55c563dd328692f5
- github.com /1Panel-dev/CordysCRM/security/advisories/GHSA-x6p7-vhgp-6r3q
- github.com /1Panel-dev/CordysCRM/releases/tag/v1.7.4
Sources
- CVE List CVE-2026-76899
- NVD CVE-2026-76899
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.