VulnerabilityModified
CVE-2020-25562
In SapphireIMS 5.0, there is no CSRF token present in the entire application.
MEDIUM 6.5EPSS 0.50%
Does this matter?
Lower severity and a low EPSS score (0.50%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- EPSS
- 0.50% probability · 41th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- sapphireims/sapphireims
- Source
- cve@mitre.org
References
- https://vuln.shellcoder.party/2020/09/19/cve-2020-25562-sapphireims-csrf/Exploit, Third Party Advisory
- https://vuln.shellcoder.party/tags/sapphireims/Third Party Advisory
- https://vuln.shellcoder.party/2020/09/19/cve-2020-25562-sapphireims-csrf/Exploit, Third Party Advisory
- https://vuln.shellcoder.party/tags/sapphireims/Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.