CVE-2020-26526 json
An issue was discovered in Damstra Smart Asset 2020.7.
published 6y ago modified 4mo ago also EUVD-2020-19071
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
An issue was discovered in Damstra Smart Asset 2020.7. It is possible to enumerate valid usernames on the login page. The application sends a different server response when the username is invalid than when the username is valid ("Unable to find an APIDomain" versus "Wrong email or password").
Is CVE-2020-26526 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.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
support.damstratechnology.com
/hc/en-us/categories/900000115446-SmartAsset-Damstra-Asset-Management-Platform
vendor-advisory
-
smartasset.com
/
vendor-advisory
-
github.com
/lukaszstu/SmartAsset-UE-CVE-2020-26526
third-party-advisory
Sources
- CVE List CVE-2020-26526
- NVD CVE-2020-26526
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.