CVE-2021-36387 json
In Yellowfin before 9.6.1 there is a Stored Cross-Site Scripting vulnerability in the video embed functionality exploitable through a speci…
published 2021-10-14 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-23002
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
In Yellowfin before 9.6.1 there is a Stored Cross-Site Scripting vulnerability in the video embed functionality exploitable through a specially crafted HTTP POST request to the page "ActivityStreamAjax.i4".
Patch / fix
- yellowfinbi yellowfin 9.6.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected products
- yellowfinbi yellowfin
Classification
References
-
wiki.yellowfinbi.com
/display/yfcurrent/Release+Notes+for+Yellowfin+9#ReleaseNotesforYellowfin9-Yellowfin9.6
release-notes, vendor-advisory
-
packetstormsecurity.com
/files/164515/Yellowfin-Cross-Site-Scripting-Insecure-Direct-Object-Reference.html
third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/164515/Yellowfin-Cross-Site-Scripting-Insecure-Direct-Object-Reference.html
third-party-advisory, vdb-entry
-
github.com
/cyberaz0r/Yellowfin-Multiple-Vulnerabilities/blob/main/README.md
third-party-advisory
-
seclists.org
/fulldisclosure/2021/Oct/15
mailing-list, third-party-advisory
- cyberaz0r.info /2021/10/yellowfin-multiple-vulnerabilities/
Sources
- CVE List CVE-2021-36387
- NVD CVE-2021-36387
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.