CVE-2026-111345 json
Trudesk through 1.2.11 Authorization Bypass via GET /api/v1/messages/conversation/:id
published 2026-10-15 24 d ago modified 2026-10-16 23 d ago also EUVD-2026-102489
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
Trudesk through 1.2.11 contains an authorization bypass vulnerability that allows any authenticated user to read private conversations by supplying another conversation's id. Attackers can request GET /api/v1/messages/conversation/:id, which lacks participant checks, to obtain full message history plus participants' usernames, full names and email addresses.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 d ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- polonel trudesk
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
hackmd.io
/@hieuPenguinnn/trudesk-conversation-messages-idor
third-party-advisory
-
github.com
/polonel/trudesk/blob/v1.2.11/src/controllers/api/v1/messages.js#L255-L308
technical-description
-
github.com
/polonel/trudesk/blob/v1.2.11/src/models/chat/message.js#L70-L101
technical-description
-
github.com
/polonel/trudesk
product
-
vulncheck.com
/advisories/trudesk-through-1.2.11-authorization-bypass-via-get-api-v1-messages-conversation-id
third-party-advisory
Sources
- CVE List CVE-2026-111345
- NVD CVE-2026-111345
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.