CVE-2021-21622 — artifact-repository-param…
MEDIUMFix: jenkinsci/artifact-repository-parameter-plugin@84b63f7CVE-2021-21622 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in io.jenkins.plugins:artifact-repository-parameter. A fix is available for io.jenkins.plugins:artifact-repository-parameter — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins Artifact Repository Parameter Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:artifact-repository-parameterReal-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 Artifact Repository Parameter Plugin 1.0.0 and earlier does not escape parameter names and descriptions.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission.
Jenkins Artifact Repository Parameter Plugin 1.0.1 escapes parameter names and descriptions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:artifact-repository-parameter | all versions | 1.0.1io.jenkins.plugins:artifact-repository-parameter:1.0.1 |
Affected Products
artifact repository parameterjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:artifact-repository-parameter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:artifact-repository-parameter to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21622 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 CVE-2021-21622 in your dependencies?
Find it across Maven, including transitive dependencies.