CVE-2020-24670
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Dashboard Editor in Hitachi Vantara Pentaho through 7.x - 8.x contains a reflected Cross-site scripting vulnerability, which allows an authenticated remote users to execute arbitrary JavaScript code. Specifically, the vulnerability lies in the 'type' attribute of 'dashboardXml' parameter. Remediated in >= 7.1.0.25, >= 8.2.0.6, and >= 8.3.0.0 GA.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHitachi Vantara Pentaho's Dashboard Editor contains a reflected Cross-site scripting (XSS) vulnerability. The vulnerability exists in the 'type' attribute of the 'dashboardXml' parameter, allowing authenticated remote attackers to inject and execute arbitrary JavaScript code in the context of the victim's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.0.0, < 7.1.0.25>= 8.0.0, < 8.2.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Pentaho server versionCheck the installed Pentaho version by inspecting the version file in the installation directory, the manifest.mf file within the pentaho WAR, or the version displayed in the Pentaho Server admin consoleAffected if The version is 7.0.0 through 7.1.0.24, or 8.0.0 through 8.2.0.5
-
Confirm Dashboard Editor is enabledVerify that the Dashboard Editor feature is available in the Pentaho user interface for authenticated usersAffected if Authenticated users have access to the Dashboard Editor functionality
-
Check for vulnerable dashboardXml endpointInspect web server logs or use a browser developer tool to confirm the dashboardXml parameter is being processed by the server in the /pentaho/api/dashboard or similar Dashboard Editor endpointsAffected if The dashboardXml parameter with a type attribute is accepted and processed by the Pentaho server
A system is affected if it runs a vulnerable Pentaho version (7.0.0-7.1.0.24 or 8.0.0-8.2.0.5) AND the Dashboard Editor is accessible to authenticated users, allowing the dashboardXml parameter to be processed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.1.0.258.2.0.6
Upgrade Pentaho to version 7.1.0.25 or higher, 8.2.0.6 or higher, or 8.3.0.0 or higher. Alternatively, implement input validation and output encoding on the dashboardXml parameter type attribute.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24670 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data