A Cross-Site Request Forgery (CSRF) vulnerability has been found in SpagoBI v3.5.1 in the user administration panel. An authenticated user can lead another user into executing unwanted actions inside the application they are logged in, like adding, editing or deleting users.
Product
eng spagobi vulnerabilities
8 published CVES affecting eng spagobi, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 1
- High
- 2
- Medium
- 4
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest eng spagobi CVEs
Newest publication first
-
MediumCVSS 6.1 EPSS 0.30%
-
MediumCVSS 5.4 EPSS 0.53%
SpagoBI v3.5.1 contains multiple Stored Cross-Site Scripting (XSS) vulnerabilities in the create/edit forms of the worksheet designer function.
-
CriticalCVSS 9.1 EPSS 13.2%
The script input feature of SpagoBI 3.5.1 allows arbitrary code execution.
-
CVE-2013-6231 SpagoBI before 4.1 has Privilege Escalation via an error in the AdapterHTTP script
PublishedHighCVSS 8.8 EPSS 9.9% Public exploitSpagoBI before 4.1 has Privilege Escalation via an error in the AdapterHTTP script
-
HighCVSS 8.0 EPSS 6.7% Public exploit
Unrestricted file upload vulnerability in the Worksheet designer in SpagoBI before 4.1 allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in an unspecified directory, aka...
-
MediumCVSS 6.8 EPSS 1.7%
The default configuration in the accessibility engine in SpagoBI 5.0.0 does not set FEATURE_SECURE_PROCESSING, which allows remote authenticated users to execute arbitrary Java code via a crafted XSL document.
-
MediumCVSS 4.3 EPSS 3.2% Public exploit
Cross-site scripting (XSS) vulnerability in SpagoBI before 4.1 allows remote authenticated users to inject arbitrary web script or HTML via the Description field in the "Short document metadata."
-
LowCVSS 3.5 EPSS 3.6% Public exploit
Cross-site scripting (XSS) vulnerability in SpagoBI before 4.1 allows remote authenticated users to inject arbitrary web script or HTML via a document note in the execution page.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.