Build Monitor ViewApplication · Jenkins
CVE-2024-28156
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 · uneditedJenkins Build Monitor View Plugin 1.14-860.vd06ef2568b_3f and earlier does not escape Build Monitor View names, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure Build Monitor Views.
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 confidenceThe Jenkins Build Monitor View Plugin versions 1.14-860.vd06ef2568b_3f and earlier fail to properly escape Build Monitor View names before rendering them in the web UI. An authenticated attacker with permissions to configure Build Monitor Views can inject malicious JavaScript code into view names, which executes in the browsers of other users who view the affected pages (stored XSS).
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
Build Monitor ViewApplication
<= 1.14-860.vd06ef2568b_3fCVSS 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.
-
Check if Build Monitor View plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, locate 'Build Monitor View' in the list, and note the version shown in the Version columnAffected if Plugin version is 1.14-860.vd06ef2568b_3f or earlier (no version number or version <= 1.14-860.vd06ef2568b_3f)
-
Identify existing Build Monitor ViewsNavigate to the Jenkins home page and look for any views listed that appear to be Build Monitor Views, typically created with the 'Build Monitor View' option when creating a new viewAffected if Any Build Monitor Views exist in the Jenkins instance
-
Inspect Build Monitor View names for injected contentClick on each Build Monitor View and examine the view name as displayed in the browser title and page header. Look for unusual characters, HTML tags, or script elements that may indicate malicious injectionAffected if View names contain unexpected HTML, JavaScript tags, or suspicious encoded characters that were not intentionally set by administrators
-
View page source to verify escapingRight-click on the Build Monitor View page, select 'View Page Source', and search for the view name in the HTML. Check if special characters like <, >, &, quotes are converted to HTML entities (e.g., < > &)Affected if View name appears in the HTML source without proper entity encoding, meaning raw special characters are present
The environment is affected if the Build Monitor View Plugin version is 1.14-860.vd06ef2568b_3f or earlier AND any Build Monitor Views exist with view names that render as executable JavaScript in the browser.
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 dataUpgrade the Jenkins Build Monitor View Plugin to version 1.14-860.vd06ef2568b_3f or later, which includes proper escaping of Build Monitor View names to prevent XSS exploitation.
Fix this in Build Monitor View
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28156 — 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-2024-28156 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