CVE-2022-36902
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 Dynamic Extended Choice Parameter Plugin 1.0.1 and earlier does not escape several fields of Moded Extended Choice 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 confidenceThe Jenkins Dynamic Extended Choice Parameter Plugin versions 1.0.1 and earlier fail to properly escape HTML/script content in multiple fields of Moded Extended Choice parameters, allowing stored XSS attacks. Attackers with Item/Configure permission can inject malicious scripts that execute when other users view the configured parameters.
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<= 1.0.1CVSS 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.
-
Confirm plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Dynamic Extended Choice Parameter', or query the plugin manager via REST: /pluginManager/api/json?tree=plugins[shortName,version]Affected if The plugin appears in the installed plugins list
-
Check plugin versionIn the Installed plugins tab, locate the Dynamic Extended Choice Parameter plugin and read the Version columnAffected if Version is 1.0.1 or earlier (the version number is less than or equal to 1.0.1)
-
Identify jobs with Moded Extended Choice parametersBrowse each job's configuration (job > Configure) and look for parameter definitions named 'Moded Extended Choice', or search job config.xml files for elements containing 'ModedExtendedChoiceParameterDefinition' or parameters that include a 'mode' attributeAffected if Any job is configured with Moded Extended Choice parameter type
-
Examine Moded Extended Choice parameter configurationsFor each job with Moded Extended Choice parameters, review the parameter fields (such as Groovy Script, Default Value, or Description) for unsanitized HTML content like <script>, <img onerror=>, javascript:, or other suspicious markupAffected if Moded Extended Choice parameters contain raw HTML or script tags in their configuration values
The environment is affected if the Dynamic Extended Choice Parameter plugin is installed at version 1.0.1 or earlier AND jobs are configured with Moded Extended Choice parameters containing unsanitized content.
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 Dynamic Extended Choice Parameter Plugin to version 1.0.2 or later, which includes proper output encoding for affected parameter fields.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36902 — 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-2022-36902 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