CVE-2020-15952: Immuta v2.8.2 is affected by stored XSS that allows a low-privileged user to escalate privileges to administra

This month

CRITICAL 9.0DOWNGRADE

CVE-2020-15952 is a critical-severity flaw (CVSS 9.0) affecting immuta. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Immuta v2.8.2 is affected by stored XSS that allows a low-privileged user to escalate privileges to administrative permissions. Additionally, unauthenticated attackers can phish unauthenticated Immuta users to steal credentials or force actions on authenticated users through reflected, DOM-based XSS.

Why this priority

Critical severity
Public exploit reference

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

Risk facts

CVSS score	9.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Weakness	CWE-79
Published	2020-11-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: immuta

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

Am I affected?

Timeline

2020-11-05 15:15 UTCPublished CVE record published
2026-06-17 02:57 UTCUpdated Record last modified

immuta immuta DOWNGRADE

Affected: 2.8.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.8.2

1. Check installed version

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

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

apt-cache madison immuta sudo apt install immuta=<VERSION_BEFORE_2.8.2> sudo apt-mark hold immuta

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

dnf --showduplicates list immuta sudo dnf downgrade immuta-<VERSION_BEFORE_2.8.2> sudo dnf versionlock add immuta

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-15952?

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

Is CVE-2020-15952 being exploited?

CVE-2020-15952 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-15952 affect?

CVE-2020-15952 affects immuta. Severity is critical (CVSS 9.0). Immuta v2.8.2 is affected by stored XSS that allows a low-privileged user to escalate privileges to administrative permissions. Additionally, unauthenticated attackers can phish unauthenticated Immuta users to steal credentials or force act

How urgent is CVE-2020-15952?

Priority 57/100. Critical severity; Public exploit reference

Related CVEs

CVE-2020-15951 MEDIUM 6.1 DOWNGRADE Immuta v2.8.2 accepts user-supplied project names without properly sanitizing the input, allowing attackers to
CVE-2020-15950 HIGH 8.8 DOWNGRADE Immuta v2.8.2 is affected by improper session management: user sessions are not revoked upon logout.
CVE-2020-15949 HIGH 7.5 DOWNGRADE Immuta v2.8.2 is affected by one instance of insecure permissions that can lead to user account takeover.

References

← Back to latest CVEs