Back to Database
Status published
Medium
CVE-2020-25562
In SapphireIMS 5.0, there is no CSRF token present in...
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-25562
Credits & Attribution
No credits recorded in the NVD database.
References
More from sapphireims
View All →CVE-2020-25566
In SapphireIMS 5.0, it is possible to take over an...
Critical
9.8
CVE-2020-25565
In SapphireIMS 5.0, it is possible to use the hardcoded...
Critical
9.8
CVE-2020-25564
In SapphireIMS 5.0, it is possible to create local administrator...
High
8.8
CVE-2020-25563
In SapphireIMS 5.0, it is possible to create local administrator...
Critical
9.8
CVE-2020-25561
SapphireIMS 5 utilized default sapphire:ims credentials to connect the client...
High
7.8
Affected Vendor
sapphireims
View all reports →Affected Software
sapphireims
Vulnerable Versions:
5.0
Timeline
Official Publish:
August 11th, 2021
Last Modified:
August 4th, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.