# CVE-2025-53661: Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form

> Attackers can view unmasked Testsigma API keys in the Jenkins job configuration form, potentially leading to unauthorized access to Testsigma services.

- **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-8wp4-r84g-gcmw

## What is CVE-2025-53661?

CVE-2025-53661 is a medium-severity vulnerability in Jenkins Testsigma Test Plan run 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 Testsigma Test Plan run Plugin 1.6 and earlier does not mask Testsigma API keys 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-53661?

2 open source packages ship an affected version, including io.jenkins.plugins:testsigma. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:testsigma` | Maven | All versions to 1.6 | None |
| `io.jenkins.plugins:testsigma` | Maven | All versions to 1.6 | None |

Products: Jenkins Testsigma Test Plan Run.

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

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

## Is CVE-2025-53661 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53661 is a medium-severity vulnerability in Jenkins Testsigma Test Plan run 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-53661 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:testsigma (Maven): affected all versions up to 1.6; no fix listed
- io.jenkins.plugins:testsigma (Maven): affected all versions up to 1.6; 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-53661/ (Markdown: https://insights.sbomify.com/CVE-2025-53661/index.md)
```

## Sources

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

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