GHSA-c2hw-w9qm-q5r9 — uno-choice
MEDIUMGHSA-c2hw-w9qm-q5r9 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.biouno:uno-choice. A fix is available for org.biouno:uno-choice — see the affected versions and patch details below.
Cross-site Scripting in Jenkins Active Choices plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-c2hw-w9qm-q5r9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.biouno:uno-choiceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Active Choices plugin version 1.5.3 and earlier allowed users with Job/Configure permission to provide arbitrary HTML to be shown on the 'Build With Parameters' page through the 'Active Choices Reactive Reference Parameter' type. This could include, for example, arbitrary JavaScript. Active Choices now sanitizes the HTML inserted on the 'Build With Parameters' page if and only if the script is executed in a sandbox. As unsandboxed scripts are subject to administrator approval, it is up to the administrator to allow or disallow problematic script output.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.biouno:uno-choice | all versions | 2.0org.biouno:uno-choice:2.0 |
Affected Products
active choicesjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.biouno:uno-choice, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.biouno:uno-choice to 2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c2hw-w9qm-q5r9 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-c2hw-w9qm-q5r9 in your dependencies?
Find it across Maven, including transitive dependencies.