dbcve.org
Business HubApplication · Knime

CVE-2025-3019

HIGH · 7.2 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 1.12.4 / 1.13.3 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
KNIME Business Hub is affected by several cross-site scripting vulnerabilities in its web pages. If a user clicks on a malicious link or opens a malicious web page, arbitrary Java Script may be executed with this user's permissions. This can lead to information loss and/or modification of existing data. The issues are caused by a bug https://github.com/Baroshem/nuxt-security/issues/610 in the widely used nuxt-security module. There are no viable workarounds therefore we strongly recommend to update to one of the following versions of KNIME Business Hub: * 1.13.3 or later * 1.12.4 or later

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 confidence

Multiple cross-site scripting (XSS) vulnerabilities in KNIME Business Hub web pages allow arbitrary JavaScript execution via malicious links, exploiting a bug in the nuxt-security module. This can lead to information disclosure and data modification with the victim's privileges.

MitigationUpdate KNIME Business Hub to version 1.13.3 or later (or 1.12.4 or later) to patch the nuxt-security module vulnerability. No workarounds are available.

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
Business HubApplication
Affected:< 1.12.4>= 1.13.0, < 1.13.3

CVSS 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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify KNIME Business Hub installation
    Locate the KNIME Business Hub installation directory or check if the service is running on your server
    Affected if KNIME Business Hub is installed and running
  2. Check installed version via web interface
    Log into the KNIME Business Hub admin or user web interface and navigate to the About, Settings, or Help section to view the product version
    Affected if Version displayed is < 1.12.4 OR >= 1.13.0 and < 1.13.3
  3. Check version via command line
    If available, use the knime or knime-business-hub command line tool with a version flag (such as 'knime --version' or 'knime-business-hub version') to retrieve the installed version
    Affected if Version output is < 1.12.4 OR >= 1.13.0 and < 1.13.3
  4. Check version in configuration files
    Inspect the version manifest, package.json, or installation metadata files typically found in the KNIME Business Hub installation directory under /conf, /lib, or /metadata
    Affected if Version recorded in files is < 1.12.4 OR >= 1.13.0 and < 1.13.3

You are affected if KNIME Business Hub is installed and the installed version falls below 1.12.4 or is between 1.13.0 and 1.13.3 (exclusive), as the nuxt-security module vulnerability in these versions allows XSS attacks via malicious links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.12.4 / 1.13.3 or later
Fixed in 1.12.41.13.3
Interim mitigation

Update KNIME Business Hub to version 1.13.3 or later (or 1.12.4 or later) to patch the nuxt-security module vulnerability. No workarounds are available.

Recommended fix High confidence

1.13.3 or later, or 1.12.4 or later

  1. 1. Back up your current KNIME Business Hub installation and all relevant data
  2. 2. Download KNIME Business Hub version 1.13.3 or later (or version 1.12.4 or later) from the official KNIME source at www.knime.com
  3. 3. Follow KNIME's official upgrade documentation to install the new version
  4. 4. Verify the installation was successful and test that the XSS vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Business Hub Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3019 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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