CVE-2020-25562 json
In SapphireIMS 5.0, there is no CSRF token present in the entire application.
published 2021-08-11 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-18246
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
In SapphireIMS 5.0, there is no CSRF token present in the entire application. This can lead to CSRF vulnerabilities in critical application forms like account resent.
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- vuln.shellcoder.party https://vuln.shellcoder.party/2020/09/19/cve-2020-25562-sapphireims-csrf/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
vuln.shellcoder.party
/2020/09/19/cve-2020-25562-sapphireims-csrf/
exploit, third-party-advisory
-
vuln.shellcoder.party
/tags/sapphireims/
third-party-advisory
Sources
- CVE List CVE-2020-25562
- NVD CVE-2020-25562
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.