dbcve.org
SitemonitorApplication · Jenkins

CVE-2022-28153

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 0.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 SiteMonitor Plugin 0.6 and earlier does not escape URLs of sites to monitor in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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 SiteMonitor Plugin versions 0.6 and earlier fails to sanitize URLs stored for monitored sites before rendering them in tooltips in the web UI. This allows an attacker with Item/Configure permission to inject malicious JavaScript code within a site URL, which executes in the browsers of other users viewing the monitoring configuration.

MitigationUpgrade the SiteMonitor plugin to a version that properly escapes URLs in tooltips (vendor fix), or implement input validation and output encoding (fn:escapeXml or similar) on all user-supplied URL fields before rendering.

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
SitemonitorApplication
Affected:<= 0.6

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
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 checks

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

  1. Verify SiteMonitor plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'SiteMonitor' or check the plugin directory $JENKINS_HOME/plugins for the sitemonitor plugin folder
    Affected if The plugin folder exists or the plugin appears in the installed list with version 0.6 or earlier
  2. Confirm the installed version
    Check the manifest file within the plugin folder: $JENKINS_HOME/plugins/sitemonitor/META-INF/MANIFEST.MF for the Plugin-Version attribute, or view the version column in Manage Plugins > Installed
    Affected if The version is 0.6 or any version lower than 0.6
  3. Identify configured monitor sites
    Navigate to the job or view where SiteMonitor is configured (the specific URL depends on your setup, typically under the job's Configure screen or a view containing monitor configured sites) and locate the monitored site URLs
    Affected if Any SiteMonitor configuration exists with URLs defined for monitoring
  4. Inspect stored URL values for injection attempts
    Access Jenkins script console (Manage Jenkins > Script Console) and run: println(jenkins.model.Jenkins.instance.getPlugin('sitemonitor')?.getExtensionList('hudson.plugins.sitemonitor.SiteMonitor')?.first()?.monitors?.toString()) to dump stored URL values, or manually inspect the configuration XML in $JENKINS_HOME/jobs/<job-name>/config.xml
    Affected if Any URL field contains unescaped HTML/JavaScript characters like <script>, javascript:, onerror=, or similar injection patterns

You are affected if the SiteMonitor plugin version is 0.6 or earlier AND there are configured monitor sites whose URLs could contain malicious JavaScript payloads that would execute when viewed in tooltips.

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 0.6
Interim mitigation

Upgrade the SiteMonitor plugin to a version that properly escapes URLs in tooltips (vendor fix), or implement input validation and output encoding (fn:escapeXml or similar) on all user-supplied URL fields before rendering.

Recommended fix Moderate confidence

SiteMonitor plugin version > 0.6 (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins
  3. 3. Click on Manage Plugins
  4. 4. Select the 'Installed' tab
  5. 5. Locate the SiteMonitor plugin in the list
  6. 6. If an update is available, click 'Update' to upgrade to a version newer than 0.6
  7. 7. Restart Jenkins if required to complete the installation

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

Fix this in Sitemonitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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