IBM Planning Analytics 2.0 could allow an attacker to obtain sensitive information due to an overly permissive CORS policy.

published 2021-01-19 5y ago modified 2026-06-17 4mo ago also EUVD-2020-26120

cvss: 5.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits: 0; none known

IBM Planning Analytics 2.0 could allow an attacker to obtain sensitive information due to an overly permissive CORS policy. IBM X-Force ID: 190836.

Patch / fix

links 1

ibm.com/support/pages/node/6404674 advisory

Is CVE-2020-4873 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.3	CVSS:3.0/PR:N/UI:N/I:N/AV:N/A:N/AC:L/C:L/S:U/E:U/RL:O/RC:C
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected products

IBM Planning Analytics

Classification

Weakness

CWE-863 Incorrect Authorization

References

ibm.com /support/pages/node/6404674
patch, vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/190836
vdb-entry, vendor-advisory

Sources

CVE List CVE-2020-4873
NVD CVE-2020-4873

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.