CVE-2020-24664
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 'pho:title' 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 confidenceA reflected Cross-site scripting (XSS) vulnerability exists in the Pentaho dashboard Editor, where user-supplied input in the 'pho:title' attribute of the 'dashboardXml' parameter is improperly handled. An authenticated attacker can inject malicious JavaScript code that executes in the context of other users' sessions when they access the crafted dashboard.
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 installed Pentaho versionLocate the Pentaho server version file (commonly version.txt in the installation directory or check the Pentaho Server startup logs) and note the exact version numberAffected if The version falls between 7.0.0 and 7.1.0.24 inclusive, or between 8.0.0 and 8.2.0.5 inclusive
-
Verify dashboard Editor is accessibleConfirm the Pentaho User Console is accessible and check if the Dashboard Editor feature is enabled for users (typically under Tools > Marketplace or Server Settings)Affected if Dashboard Editor is available and users have permission to create or edit dashboards
-
Confirm authentication is in useVerify that the Pentaho server requires authentication (check web.xml or pentahoObjects.spring.xml for security configuration, or confirm login is required to access the dashboard Editor)Affected if Users can authenticate to the Pentaho User Console, as the attack requires an authenticated session
-
Check for dashboardXml parameter exposureReview web server access logs or proxy logs for requests containing the 'dashboardXml' parameter, particularly those with 'pho:title' attributesAffected if The dashboardXml parameter is being processed by the server without sanitization of the pho:title attribute value
-
Review dashboard rendering behaviorIf possible, examine how dashboards are rendered by creating a test dashboard with special characters in the title and observing if they are encoded or reflected raw in the outputAffected if Special characters in dashboard titles are reflected without proper HTML encoding
A user is affected if they are running Pentaho versions 7.0.0 through 7.1.0.24 or 8.0.0 through 8.2.0.5, the dashboard Editor is accessible to authenticated users, and the dashboardXml parameter handles the pho:title attribute without sanitization.
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 to Pentaho versions >= 7.1.0.25, >= 8.2.0.6, or >= 8.3.0.0. Alternatively, implement strict input validation and output encoding on the dashboardXml parameter before rendering.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24664 — 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-24664 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