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.
CVE-2026-76899
MEDIUMPre-NVD 5.75.7
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.7
- EG Score
- 5.7(low)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity57% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (5)
Auto-updated Sep 18, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
v1.7.4
Patch available: 1Panel-dev/CordysCRM v1.7.4
https://github.com/1Panel-dev/CordysCRM/releases/tag/v1.7.4github_commit Patch Available
commit b217166af293 (1Panel-dev/CordysCRM)
Patch available: 1Panel-dev/CordysCRM v1.8.0 (contains commit b217166af293)
https://github.com/1Panel-dev/CordysCRM/commit/b217166af2935c827c8d73bf55c563dd328692f5github_commit Patch Available
commit 3e6a7003ac5c (1Panel-dev/CordysCRM)
Patch available: 1Panel-dev/CordysCRM v1.7.4 (contains commit 3e6a7003ac5c)
https://github.com/1Panel-dev/CordysCRM/commit/3e6a7003ac5c94bc1166c6065e64420be2f188a8github_pr Patch Available
refactor: remove deprecated configuration properties
Patch available: 1Panel-dev/CordysCRM v1.7.4 (PR #2975 merged 2026-07-09)
https://github.com/1Panel-dev/CordysCRM/pull/2975github Patch Available🟡 PoC Available
Authenticated SQL injection via `sort.name` on `POST /account-pool/page` · Advisory · 1Panel-dev/CordysCRM · GitHub
https://github.com/1Panel-dev/CordysCRM/security/advisories/GHSA-x6p7-vhgp-6r3qWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 20:30 UTCEG score recompute
- 2026-09-18 20:10 UTCEG score recompute
- 2026-09-18 20:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-76899?
CVE-2026-76899 is a medium vulnerability published on September 18, 2026. 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 MODULESETTINGUPDATE to place an arbitrary database function in SortRequest.name because…
When was CVE-2026-76899 disclosed?
CVE-2026-76899 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76899 actively exploited?
CVE-2026-76899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-76899?
CVE-2026-76899 has a CVSS v3 base score of 5.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-76899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76899, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76899
Is Your Infrastructure Affected by CVE-2026-76899?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.