CVE-2022-34780 — xlrelease-plugin
MEDIUMCVE-2022-34780 is a medium-severity (CVSS 5.4) Cross-Site Request Forgery (CSRF) vulnerability in com.xebialabs.ci:xlrelease-plugin. A fix is available for com.xebialabs.ci:xlrelease-plugin — see the affected versions and patch details below.
CSRF vulnerability in Jenkins XebiaLabs XL Release Plugin allow capturing credentials
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
com.xebialabs.ci:xlrelease-pluginReal-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
XebiaLabs XL Release Plugin 22.0.0 and earlier does not perform permission checks in methods implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
XebiaLabs XL Release Plugin 22.0.1 requires POST requests and Overall/Administer permission for the affected form validation methods.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.xebialabs.ci:xlrelease-plugin | all versions | 22.0.1com.xebialabs.ci:xlrelease-plugin:22.0.1 |
Affected Products
xebialabs xl releasejenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.xebialabs.ci:xlrelease-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.xebialabs.ci:xlrelease-plugin to 22.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34780 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-34780 in your dependencies?
Find it across Maven, including transitive dependencies.