dbcve.org
Multiselect ParameterWordPress extension · Jenkins

CVE-2022-30964

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 1.3 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 Multiselect parameter Plugin 1.3 and earlier does not escape the name and description of Multiselect parameters on views displaying parameters, 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 Multiselect parameter Plugin versions 1.3 and earlier contains a stored cross-site scripting (XSS) vulnerability. The plugin fails to properly escape the name and description fields of Multiselect parameters when rendering them in the parameter display views. Attackers with Item/Configure permission can inject malicious JavaScript code through these fields, which will execute when other users view the parameters.

MitigationUpgrade the Multiselect parameter Plugin to version 1.4 or later, which includes proper HTML escaping of parameter names and descriptions. As a compensating control, limit Item/Configure permissions to trusted users only until the upgrade 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
Multiselect ParameterWordPress extension
Affected:<= 1.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
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 Multiselect Parameter plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin manifest file at $JENKINS_HOME/plugins/multiselect-parameter.jpi or $JENKINS_HOME/plugins/multiselect-parameter/MANIFEST.MF
    Affected if The plugin appears in the installed plugins list with a version number of 1.3 or earlier
  2. Confirm the plugin version number
    Locate the plugin version in the Jenkins plugin manager UI under the 'Version' column, or read the Version attribute from the plugin manifest file
    Affected if The installed version is 1.3 or any version lower than 1.3 (for example, 1.0, 1.1, 1.2, 1.3)
  3. Identify jobs using Multiselect parameters
    Review job configurations in Jenkins to see if any jobs define Multiselect parameter definitions, or inspect job config.xml files for <org.jenkinsci.plugins.multiselectparameter> entries
    Affected if Any Jenkins jobs are configured to use Multiselect parameters from this plugin
  4. Check permission assignments for Item/Configure
    Review Jenkins authorization matrix or folder-based permissions to identify which users or groups have Item/Configure or Job/Configure permissions
    Affected if Users other than Jenkins administrators have Item/Configure permission, as this permission level is required to inject the malicious payload

You are affected if the Multiselect Parameter plugin version is 1.3 or earlier AND Multiselect parameters are used in any job AND users with Item/Configure permission exist beyond trusted administrators.

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

Upgrade the Multiselect parameter Plugin to version 1.4 or later, which includes proper HTML escaping of parameter names and descriptions. As a compensating control, limit Item/Configure permissions to trusted users only until the upgrade can be applied.

Recommended fix Moderate confidence

Multiselect Parameter Plugin version 1.4

  1. Log in to the Jenkins controller as an administrator with Manage Plugins permission
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Locate the 'Multiselect Parameter' plugin in the list
  5. If the plugin shows an update is available, select it and click 'Download now and install after restart'
  6. Alternatively, check the 'Available' tab for version 1.4 or later and install it
  7. Restart Jenkins to complete the plugin update
  8. Verify the plugin is updated to version 1.4 or later in the installed plugins list

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

Fix this in Multiselect Parameter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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