CVE-2026-108704
CordysCRM through 1.9.3 Authorization Bypass via Follow-Up Record Add Endpoints
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
CordysCRM through 1.9.3 contains an authorization bypass vulnerability that allows low-privileged authenticated users to skip permission checks by setting the owner field to their own user id. Attackers can send requests to the follow/record/add endpoints to add follow-up records and overwrite follow_time and follower on any known customer, clue or opportunity.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- 1Panel-dev CordysCRM
through 1.9.3
References 6
GitHub · AnkesKasty/cve-request-poc
GitHub · 1Panel-dev/CordysCRM
- backend/crm/src/main/java/cn/cordys/crm/customer/controller/CustomerFollowRecordController.java · L35-L41
- backend/crm/src/main/java/cn/cordys/crm/follow/controller/FollowUpRecordController.java · L85-L91
- backend/crm/src/main/java/cn/cordys/crm/clue/controller/ClueFollowRecordController.java · L33-L39
- backend/crm/src/main/java/cn/cordys/crm/follow/service/BaseFollowUpService.java · L198-L204