# CVE-2025-53675: Jenkins Warrior Framework Plugin vulnerability exposes unencrypted passwords to certain authenticated users

> Attackers with specific permissions or file system access can view unencrypted passwords stored in Jenkins job configuration files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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-2g8w-9933-36vr

## What is CVE-2025-53675?

CVE-2025-53675 is a medium-severity vulnerability in Jenkins Warrior Framework 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 Warrior Framework Plugin 1.2 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

Weakness: CWE-256 (Plaintext Storage of a Password)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:warrior` | Maven | All versions to 1.2 | None |
| `org.jenkins-ci.plugins:warrior` | Maven | All versions to 1.2 | None |

Products: Jenkins Warrior Framework.

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

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

## Is CVE-2025-53675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53675 is a medium-severity vulnerability in Jenkins Warrior Framework 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-53675 in the wild and no public exploit code.

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

## Sources

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

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