dbcve.org
PlotApplication · Jenkins

CVE-2022-34783

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to after 2.1.10 or later.
See remediation →
58/100
Remediation priority · Elevated
High EPSS 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 Plot Plugin 2.1.10 and earlier does not escape plot descriptions, 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 Plot Plugin versions 2.1.10 and earlier contain a stored cross-site scripting (XSS) vulnerability where plot descriptions are not properly escaped before being rendered in web pages. Attackers with Item/Configure permission can inject malicious JavaScript code into plot descriptions that will execute when other users view the affected plot.

MitigationUpdate Jenkins Plot Plugin to version 2.1.11 or later which implements proper escaping of plot descriptions. As a compensating control, restrict Item/Configure permission to trusted users only until the patch can be applied.

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
PlotApplication
Affected:<= 2.1.10

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 Plot Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Plot' or access the Jenkins script console and run: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'plot' }
    Affected if Plot Plugin does not appear in the installed plugins list (not affected)
  2. Determine installed Plot Plugin version
    In Manage Jenkins > Manage Plugins > Installed tab, locate the Plot Plugin and note the Version column, or run via script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'plot' }.version
    Affected if Version is 2.1.10 or lower (vulnerable)
  3. Check for plot configurations with descriptions
    Navigate to job configurations that use the Plot plugin and inspect any Plot build step or publisher. Look for the 'Plot Description' field in the plot configuration.
    Affected if Plot configurations exist where the Description field accepts user input (potential XSS vector)
  4. Confirm Description field processing
    Review if plot descriptions are entered by users with Item/Configure permission. The vulnerability requires that an attacker can input malicious script into the description field.
    Affected if Users with Item/Configure permission can create or modify plot descriptions

User is affected if Jenkins Plot Plugin version is 2.1.10 or earlier AND plot configurations exist where users can input descriptions, since unsanitized description content enables stored XSS execution.

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

Update Jenkins Plot Plugin to version 2.1.11 or later which implements proper escaping of plot descriptions. As a compensating control, restrict Item/Configure permission to trusted users only until the patch can be applied.

Recommended fix High confidence

Plot Plugin version 2.1.11 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Search for 'Plot' in the plugin list
  4. 4. If Plot Plugin is installed, check if version is 2.1.10 or earlier
  5. 5. Go to the 'Available' tab and search for 'Plot Plugin'
  6. 6. If a newer version is available, select it and click 'Install'
  7. 7. Alternatively, download the latest .hpi file from the Jenkins plugin repository (https://plugins.jenkins.io/plot/)
  8. 8. Navigate to Manage Jenkins > Manage Plugins > Advanced

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

Fix this in Plot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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