CVE-2022-3960
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 · uneditedHitachi Vantara Pentaho Business Analytics Server prior to versions 9.4.0.1 and 9.3.0.2, including 8.3.x cannot allow a system administrator to disable scripting capabilities of the Community Dashboard Editor (CDE) plugin.
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 Business Analytics Server prior to versions 9.4.0.1 and 9.3.0.2 lacks the ability for system administrators to disable scripting capabilities within the Community Dashboard Editor (CDE) plugin, potentially allowing execution of arbitrary scripts.
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< 9.3.0.2= 9.4.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Locate Pentaho BA Server installation and versionCheck the Pentaho server installation directory for version information. Common locations include version files, manifest files, or the pentaho-solutions/system/server.properties file. The version may also be visible in server startup logs.Affected if The installed version is less than 9.3.0.2, or equal to 9.4.0.0 (for example, 9.4.0.0, 9.2.0.1, 9.1.0.0, etc.)
-
Identify if CDE plugin is deployedCheck for the presence of the CDE (Community Dashboard Editor) plugin in the Pentaho server. This is typically found in the pentaho-solutions/system/cde directory or as a Pentaho Marketplace plugin.Affected if The CDE plugin is installed and accessible to users in the Pentaho BA Server.
-
Verify CDE scripting is not explicitly disabledIn vulnerable versions, there is no administrative setting to disable scripting within CDE. Check for any custom configuration files (such as in system/cde or plugin configuration) that might attempt to restrict script execution. In the affected versions, such controls do not exist by design.Affected if There is no configuration option available to disable or restrict CDE scripting capabilities (this is the core vulnerability in affected versions).
A user is affected if they run Pentaho BA Server versions 9.4.0.0 or any version prior to 9.3.0.2, and the CDE plugin is installed and accessible to users in their environment.
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.
dbcve · scoped9.3.0.2
Upgrade to Pentaho Business Analytics Server versions 9.4.0.1 or 9.3.0.2 which add the capability to disable CDE scripting. If immediate upgrade is not feasible, restrict access to the CDE plugin to trusted users only and monitor for unauthorized dashboard modifications.
Pentaho Business Analytics Server 9.4.0.1 or later (or 9.3.0.2 or later for the 9.3.x branch)
- 1. Backup your current Pentaho Business Analytics Server configuration and data
- 2. Download Pentaho Business Analytics Server version 9.4.0.1 or later (or version 9.3.0.2 or later for the 9.3.x branch) from the official Hitachi Vantara support portal
- 3. Stop the Pentaho Server service
- 4. Upgrade the Pentaho installation to the chosen fixed version following the standard upgrade documentation
- 5. After upgrade, verify that the CDE plugin scripting disable functionality is now available in the administrator settings
- 6. Test that the disable scripting feature works correctly and restart the server
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3960 — 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-2022-3960 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