CVE-2019-20484 json
An issue was discovered in Viki Vera 4.9.1.26180.
published 5y ago modified 4mo ago also EUVD-2019-11028
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
An issue was discovered in Viki Vera 4.9.1.26180. A user without access to a project could download or upload project files by opening the Project URL directly in the browser after logging in.
Is CVE-2019-20484 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
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gosecure.net https://www.gosecure.net/blog/2020/12/15/vera-stored-xss-improper-access-control/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-425 Direct Request
References
-
gosecure.net
/blog/2020/12/15/vera-stored-xss-improper-access-control/
exploit, third-party-advisory
Sources
- CVE List CVE-2019-20484
- NVD CVE-2019-20484
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.