CVE-2020-19586: Incorrect Access Control issue in Yellowfin Business Intelligence 7.3 allows remote attackers to escalate priv

This month

CRITICAL 9.0DOWNGRADE

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

Incorrect Access Control issue in Yellowfin Business Intelligence 7.3 allows remote attackers to escalate privilege via MIAdminStyles.i4 Admin UI.

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	1.5% (top 25%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-09-14
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: yellowfinbi

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

Am I affected?

Timeline

2022-09-14 03:15 UTCPublished CVE record published
2026-06-17 02:59 UTCUpdated Record last modified

yellowfinbi business intelligence DOWNGRADE

Affected: 7.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.3

1. Check installed version

apt-cache policy business-intelligence || rpm -q business-intelligence || business-intelligence --version

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

apt-cache madison business-intelligence sudo apt install business-intelligence=<VERSION_BEFORE_7.3> sudo apt-mark hold business-intelligence

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

dnf --showduplicates list business-intelligence sudo dnf downgrade business-intelligence-<VERSION_BEFORE_7.3> sudo dnf versionlock add business-intelligence

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

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

Is CVE-2020-19586 being exploited?

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

CVE-2020-19586 affects business intelligence. Severity is critical (CVSS 9.0). Incorrect Access Control issue in Yellowfin Business Intelligence 7.3 allows remote attackers to escalate privilege via MIAdminStyles.i4 Admin UI.

How urgent is CVE-2020-19586?

Priority 55/100. Critical severity; Public exploit reference

Related CVEs

CVE-2026-60671 HIGH 8.6 DOWNGRADE Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: B
CVE-2026-60674 HIGH 8.2 DOWNGRADE Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: B
CVE-2026-61302 HIGH 8.2 DOWNGRADE Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: P
CVE-2026-71055 HIGH 8.8 DOWNGRADE Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: P
CVE-2026-71061 HIGH 7.5 DOWNGRADE Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: B

References

← Back to latest CVEs