Missing permission check in Jenkins XebiaLabs XL Deploy Plugin allows capturing credentials

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2021-21663: 1.00% estimated exploitation activity in the next 30 days; percentile 62.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A missing permission check in Jenkins XebiaLabs XL Deploy Plugin 7.5.8 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing Username/password credentials stored in Jenkins.

Published by the source

24 May 2022, 19:04 UTC

Last modified by the source

27 Oct 2023, 15:17 UTC

Source last checked

26 Oct 2026, 16:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6mpp-cm3v-23vv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-21663

Advisory: Missing permission check in Jenkins XebiaLabs XL Deploy Plugin allows capturing credentials
IDs: CVE-2021-21663, GHSA-6mpp-cm3v-23vv
Record: https://patchnext.com/advisories/cve-2021-21663 (revision 1, source checked 26 Oct 2026, 16:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.xebialabs.deployit.ci:deployit-plugin 10.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.xebialabs.deployit.ci:deployit-plugin: affected <= 10.0.1; fixed in 10.0.2

## Suggested inspection (read-only)
- Maven com.xebialabs.deployit.ci:deployit-plugin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.xebialabs.deployit.ci:deployit-plugin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6mpp-cm3v-23vv (GitHub-reviewed advisory GHSA-6mpp-cm3v-23vv lists affected ranges: Maven com.xebialabs.deployit.ci:deployit-plugin >=0 <=10.0.1)

Commands are suggestions: review each one before running it.