dbcve.org
Autocomplete ParameterApplication · Jenkins

CVE-2022-30961

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 1.1 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 Autocomplete Parameter Plugin 1.1 and earlier does not escape the name of Dropdown Autocomplete and Auto Complete String 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 Autocomplete Parameter Plugin versions 1.1 and earlier fails to properly escape the name field of Dropdown Autocomplete and Auto Complete String parameters when rendering them in parameter views. This allows an attacker with Item/Configure permission to inject malicious JavaScript code into the parameter name, which executes in the browsers of other users who view those parameters.

MitigationUpgrade the Jenkins Autocomplete Parameter Plugin to version 1.2 or later, which implements proper output encoding for parameter names.

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
Autocomplete ParameterApplication
Affected:<= 1.1

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. Check if Autocomplete Parameter plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab. Search for 'Autocomplete Parameter' and note the version listed.
    Affected if The plugin is installed and the version is 1.1 or earlier.
  2. Identify jobs using vulnerable parameter types
    Review Jenkins jobs for configured parameters of type 'Dropdown Autocomplete' or 'Auto Complete String'. This can be done by viewing individual job configurations under the Parameters section.
    Affected if Any job is configured with Dropdown Autocomplete or Auto Complete String parameters.
  3. Check if untrusted users have Item/Configure permission
    Navigate to Manage Jenkins > Manage Users and review which users have overall or item-level permissions. Specifically check if users without administrative access have Item/Configure or Job/Configure permissions.
    Affected if Untrusted or non-administrative users have Item/Configure permission and can access jobs with the vulnerable parameters.

You are affected if the Autocomplete Parameter plugin version 1.1 or earlier is installed AND Dropdown Autocomplete or Auto Complete String parameters are in use, allowing an attacker with Item/Configure permission to inject malicious script into parameter names.

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.1
Interim mitigation

Upgrade the Jenkins Autocomplete Parameter Plugin to version 1.2 or later, which implements proper output encoding for parameter names.

Recommended fix Moderate confidence

Version 1.2 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Click on the 'Installed' tab
  4. Locate the 'Autocomplete Parameter' plugin in the list
  5. If an update is available, select the plugin and click 'Update'
  6. Alternatively, download the fixed version from the Jenkins plugin repository (https://plugins.jenkins.io/)
  7. Restart Jenkins if required after the update

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

Fix this in Autocomplete Parameter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 h
3.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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