dbcve.org
Health Advisor By CloudbeesApplication · Jenkins

CVE-2025-47885

HIGH · 8.8 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to after 374.v194b_d4f0c8c8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Jenkins Health Advisor by CloudBees Plugin 374.v194b_d4f0c8c8 and earlier does not escape responses from the Jenkins Health Advisor server, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control Jenkins Health Advisor server responses.

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

The Jenkins Health Advisor by CloudBees Plugin versions 374.v194b_d4f0c8c8 and earlier fails to escape/sanitize responses returned from the Jenkins Health Advisor server. This allows an attacker with control over the Health Advisor server to inject malicious JavaScript into the plugin's output, which executes in the browsers of users viewing the data, resulting in stored XSS.

MitigationUpdate the Jenkins Health Advisor by CloudBees Plugin to the latest version once available. If immediate update is not possible, restrict network access to the Health Advisor server and implement Content Security Policy headers as compensating controls.

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
Health Advisor By CloudbeesApplication
Affected:<= 374.v194b_d4f0c8c8

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify the Jenkins Health Advisor by CloudBees plugin is installed
    Log into Jenkins as an administrator, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Health Advisor by CloudBees', or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.contains('cloudbees-health-advisor-client-plugin')
    Affected if The plugin is not installed or not found in the installed plugins list.
  2. Check the installed version of the plugin
    In the Manage Plugins > Installed tab, locate the CloudBees Health Advisor plugin and note the version column. Alternatively, use the Jenkins script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'cloudbees-health-advisor-client-plugin'?.version
    Affected if Version is 374.v194b_d4f0c8c8 or earlier (the affected version range).
  3. Determine if the plugin is configured with a Health Advisor server
    Go to Manage Jenkins > Configure System and look for the CloudBees Health Advisor configuration section. Check if a Health Advisor server URL is configured and the connection is enabled. Alternatively, check the Jenkins configuration file (jenkins.model.Jenkins.location?.configuration) or inspect the plugin's configuration via the script console: Jenkins.instance.getDescriptorByType(com.cloudbees.jenkins.plugins.health.HealthAdvisorGlobalDescriptor).healthAdvisorServer
    Affected if A Health Advisor server URL is configured and the plugin is actively retrieving data from it (the XSS payload would be delivered through this connection).

You are affected if the CloudBees Health Advisor plugin is installed with version 374.v194b_d4f0c8c8 or earlier AND a Health Advisor server is configured to provide data to the plugin.

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 a release after 374.v194b_d4f0c8c8
Interim mitigation

Update the Jenkins Health Advisor by CloudBees Plugin to the latest version once available. If immediate update is not possible, restrict network access to the Health Advisor server and implement Content Security Policy headers as compensating controls.

Recommended fix Moderate confidence

Latest available version of Health Advisor by CloudBees plugin (version higher than 374.v194b_d4f0c8c8)

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Locate the 'Health Advisor by CloudBees' plugin in the 'Installed' tab
  3. Check the current version to confirm it is 374.v194b_d4f0c8c8 or earlier
  4. Upgrade to the latest available version of the Health Advisor by CloudBees plugin
  5. Restart Jenkins if required to complete the plugin update
  6. Verify the upgrade was successful by checking the plugin version
Caveat Review release notes for any breaking changes or configuration requirements in newer versions

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

Fix this in Health Advisor By Cloudbees Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47885 — 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-47885 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