# CVE-2025-47887: Jenkins Cadence vManager Plugin is Missing Permission Checks

> Attackers with read access can bypass permission checks to connect to arbitrary URLs using provided credentials, potentially exposing sensitive data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** Yes
- **Published:** 14 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-rf73-97j8-9vqh

## What is CVE-2025-47887?

CVE-2025-47887 is a medium-severity missing authorization vulnerability in Jenkins Cadence vManager Plugin, published on 14 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing permission checks in Jenkins Cadence vManager Plugin 4.0.1-286.v9e25a_740b_a_48 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified username and password.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:vmanager-plugin` | Maven | All versions | 4.0.1-288.v8804b_ea_a_cb_7f |
| `org.jenkins-ci.plugins:vmanager-plugin` | Maven | All versions | 4.0.1-288.v8804b_ea_a_cb_7f |

Products: Jenkins Cadence Vmanager.

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

Upgrade org.jenkins-ci.plugins:vmanager-plugin to 4.0.1-288.v8804b_ea_a_cb_7f or later.

## Is CVE-2025-47887 being exploited?

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

## Other vulnerabilities in Jenkins Cadence vManager Plugin

- [CVE-2019-10446](https://insights.sbomify.com/CVE-2019-10446/): Jenkins Cadence vManager Plugin disables SSL/TLS and hostname verification (high 8.2)
- [CVE-2020-2243](https://insights.sbomify.com/CVE-2020-2243/): Stored XSS vulnerability in Jenkins Cadence vManager Plugin (medium 5.4)
- [CVE-2025-47886](https://insights.sbomify.com/CVE-2025-47886/): Jenkins Cadence vManager Plugin Vulnerable to Cross-Site Request Forgery (medium 4.3)
- [CVE-2025-31724](https://insights.sbomify.com/CVE-2025-31724/): Jenkins Cadence vManager Plugin Stores Verisium Manager vAPI keys Unencrypted (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47887 is a medium-severity missing authorization vulnerability in Jenkins Cadence vManager Plugin, published on 14 May 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-47887 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:vmanager-plugin (Maven): affected all versions; fixed in 4.0.1-288.v8804b_ea_a_cb_7f
- org.jenkins-ci.plugins:vmanager-plugin (Maven): affected all versions; fixed in 4.0.1-288.v8804b_ea_a_cb_7f

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-47887/ (Markdown: https://insights.sbomify.com/CVE-2025-47887/index.md)
```

## Sources

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

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