CVE-2009-5099 json
Cross-site scripting (XSS) vulnerability in ViewAction in Pentaho BI Server 1.7.0.1062 and earlier allows remote attackers to inject arbitr…
published 15y ago modified 4mo ago also EUVD-2009-5054
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in ViewAction in Pentaho BI Server 1.7.0.1062 and earlier allows remote attackers to inject arbitrary web script or HTML via the outputType parameter.
Is CVE-2009-5099 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 FencerExploit prediction
1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- jira.pentaho.com http://jira.pentaho.com/browse/BISERVER-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel referenced PoC, tagged "exploit" by a source, unverified
- antisnatchor.com http://antisnatchor.com/2009/06/20/pentaho-1701062-multiple-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
jira.pentaho.com
/browse/BISERVER-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
exploit
-
antisnatchor.com
/2009/06/20/pentaho-1701062-multiple-vulnerabilities/
exploit
-
secunia.com
/advisories/37024
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/2972
vdb-entry, vendor-advisory
-
securityfocus.com
/archive/1/507168/100/0/threaded
mailing-list
Sources
- CVE List CVE-2009-5099
- NVD CVE-2009-5099
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.