CVE-2020-25562: In SapphireIMS 5.0, there is no CSRF token present in the entire application

Routine

MEDIUM 6.5DOWNGRADE

CVE-2020-25562 is a medium-severity flaw (CVSS 6.5) affecting sapphireims. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-352
Published	2021-08-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: sapphireims

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-08-11 21:15 UTCPublished CVE record published
2026-06-17 03:06 UTCUpdated Record last modified

sapphireims sapphireims DOWNGRADE

Affected: 5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0

1. Check installed version

apt-cache policy sapphireims || rpm -q sapphireims || sapphireims --version

2. No fixed release: DOWNGRADE to a release before 5.0 (Debian / Ubuntu)

apt-cache madison sapphireims sudo apt install sapphireims=<VERSION_BEFORE_5.0> sudo apt-mark hold sapphireims

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sapphireims sudo dnf downgrade sapphireims-<VERSION_BEFORE_5.0> sudo dnf versionlock add sapphireims

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-25562?

sapphireims: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-25562 being exploited?

CVE-2020-25562 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-25562 affect?

CVE-2020-25562 affects sapphireims. Severity is medium (CVSS 6.5). 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.

How urgent is CVE-2020-25562?

Priority 38/100. Public exploit reference

Related CVEs

CVE-2020-25566 CRITICAL 9.8 DOWNGRADE In SapphireIMS 5.0, it is possible to take over an account by sending a request to the Save_Password form as s
CVE-2020-25565 CRITICAL 9.8 DOWNGRADE In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password: i
CVE-2020-25564 HIGH 8.8 DOWNGRADE In SapphireIMS 5.0, it is possible to create local administrator on any client with credentials of a non-privi
CVE-2020-25563 CRITICAL 9.8 DOWNGRADE In SapphireIMS 5.0, it is possible to create local administrator on any client without requiring any credentia
CVE-2020-25561 HIGH 7.8 DOWNGRADE SapphireIMS 5 utilized default sapphire:ims credentials to connect the client to server

References

← Back to latest CVEs