CVE-2020-11463 json
An issue was discovered in Deskpro before 2019.8.0.
published 6y ago modified 4mo ago also EUVD-2020-3817
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
An issue was discovered in Deskpro before 2019.8.0. The /api/email_accounts endpoint failed to properly validate a user's privilege, allowing an attacker to retrieve cleartext credentials of all helpdesk email accounts, including incoming and outgoing email credentials. This enables an attacker to get full access to all emails sent or received by the system including password reset emails, making it possible to reset any user's password.
Patch / fix
- deskpro deskpro 2019.8.0
Is CVE-2020-11463 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.83% chance of exploitation in the next 30 days, higher than 78% 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 |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-862 Missing Authorization
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-11463
- NVD CVE-2020-11463
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.