SAP BusinessObjects Business Intelligence Platform (Web Services) versions - 410, 420, 430, allows an unauthenticated attacker to inject ar…

published 2020-10-20 6y ago modified 2026-06-17 4mo ago also EUVD-2020-27458

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

SAP BusinessObjects Business Intelligence Platform (Web Services) versions - 410, 420, 430, allows an unauthenticated attacker to inject arbitrary values as CMS parameters to perform lookups on the internal network which is otherwise not accessible externally. On successful exploitation, attacker can scan internal network to determine internal infrastructure and gather information for further attacks like remote file inclusion, retrieve server files, bypass firewall and force the vulnerable server to perform malicious requests, resulting in a Server-Side Request Forgery vulnerability.

Is CVE-2020-6308 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

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

Exploits and checks

Nuclei template SAP BusinessObjects Business Intelligence Platform - Blind Server-Side Request Forgery nuclei detection template

CVSS scores

assigned by	version	score	vector
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	3.1	5.3	CVSS:3.1/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

SAP SE SAP BusinessObjects Business Intelligence Platform (Web Services)

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

wiki.scn.sap.com /wiki/pages/viewpage.action?pageId=558632196
vendor-advisory
launchpad.support.sap.com /#/notes/2943844
permissions-required, vendor-advisory

Sources

CVE List CVE-2020-6308
NVD CVE-2020-6308

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.