Passwords transmitted in plain text by Jenkins ReadyAPI Functional Testing Plugin

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-2020-2251: 0.51% estimated exploitation activity in the next 30 days; percentile 43.86 (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.

ReadyAPI Functional Testing Plugin stores project passwords in job config.xml files on the Jenkins controller as part of its configuration. While these passwords are stored encrypted on disk since ReadyAPI Functional Testing Plugin 1.4, they are transmitted in plain text as part of the global configuration form by ReadyAPI Functional Testing Plugin 1.5 and earlier. These passwords can be viewed by attackers with Extended Read permission. This only affects Jenkins before 2.236, including 2.235.x LTS, as Jenkins 2.236 introduces a security hardening that transparently encrypts and decrypts data used for a Jenkins password form field.

Published by the source

24 May 2022, 17:27 UTC

Last modified by the source

26 Oct 2023, 23:37 UTC

Source last checked

26 Oct 2026, 16:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q4qq-8q2r-g2f2

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

# Patch Next advisory brief: CVE-2020-2251

Advisory: Passwords transmitted in plain text by Jenkins ReadyAPI Functional Testing Plugin
IDs: CVE-2020-2251, GHSA-q4qq-8q2r-g2f2
Record: https://patchnext.com/advisories/cve-2020-2251 (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: org.jenkins-ci.plugins:soapui-pro-functional-testing 1.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:soapui-pro-functional-testing: affected <= 1.5; fixed in 1.6

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:soapui-pro-functional-testing: 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 org.jenkins-ci.plugins:soapui-pro-functional-testing.
- 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-q4qq-8q2r-g2f2 (GitHub-reviewed advisory GHSA-q4qq-8q2r-g2f2 lists affected ranges: Maven org.jenkins-ci.plugins:soapui-pro-functional-testing >=0 <=1.5)

Commands are suggestions: review each one before running it.