CVE-2020-11466 json
An issue was discovered in Deskpro before 2019.8.0.
published 6y ago modified 4mo ago also EUVD-2020-3820
- cvss
- 7.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
An issue was discovered in Deskpro before 2019.8.0. The /api/tickets endpoint failed to properly validate a user's privilege, allowing an attacker to retrieve arbitrary information about all helpdesk tickets stored in database with numerous filters. This leaked sensitive information to unauthorized parties. Additionally, it leaked ticket authentication code, making it possible to make changes to a ticket.
Patch / fix
- deskpro deskpro 2019.8.0
Is CVE-2020-11466 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.redforce.io https://blog.redforce.io/attacking-helpdesks-part-1-rce-chain-on-deskpro/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.6 | CVSS:3.0/AC:L/AV:N/A:L/C:H/I:L/PR:L/S:U/UI:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 7.6 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
blog.redforce.io
/attacking-helpdesks-part-1-rce-chain-on-deskpro/
exploit, third-party-advisory
-
support.deskpro.com
/en/news/posts/deskpro-v2019-8-0-released-security-update
release-notes, vendor-advisory
-
support.deskpro.com
/en/news/posts/deskpro-security-update-2019-09
release-notes, vendor-advisory
Sources
- CVE List CVE-2020-11466
- NVD CVE-2020-11466
Fencer Intel 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.