# CVE-2025-53657: Jenkins ReadyAPI Functional Testing Plugin vulnerability exposes secrets

> Attackers can view sensitive credentials like license keys and passwords in the Jenkins job configuration form due to lack of masking.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-r496-x769-f8j4

## What is CVE-2025-53657?

CVE-2025-53657 is a medium-severity vulnerability in Jenkins ReadyAPI Functional Testing Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins ReadyAPI Functional Testing Plugin 1.11 and earlier does not mask SLM License Access Keys, client secrets, and passwords displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2025-53657?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:soapui-pro-functional-testing. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:soapui-pro-functional-testing` | Maven | All versions to 1.11 | None |
| `org.jenkins-ci.plugins:soapui-pro-functional-testing` | Maven | All versions to 1.11 | None |

Products: Jenkins Readyapi Functional Testing.

## How do I fix CVE-2025-53657?

No fix has been published for CVE-2025-53657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53657 being exploited?

There is no known exploitation of CVE-2025-53657 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins ReadyAPI Functional Testing Plugin

- [CVE-2025-53656](https://insights.sbomify.com/CVE-2025-53656/): Jenkins ReadyAPI Functional Testing Plugin vulnerability stores unencrypted authentication credentials (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53657 and fix it if it is affected.

What it is: CVE-2025-53657 is a medium-severity vulnerability in Jenkins ReadyAPI Functional Testing Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53657 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:soapui-pro-functional-testing (Maven): affected all versions up to 1.11; no fix listed
- org.jenkins-ci.plugins:soapui-pro-functional-testing (Maven): affected all versions up to 1.11; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53657/ (Markdown: https://insights.sbomify.com/CVE-2025-53657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53657
- OSV: https://osv.dev/vulnerability/CVE-2025-53657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53657/
Summaries are generated and may contain mistakes; the official description above is the record.