Attacker-directed connections via CSRF-prone validation methods
Published May 14, 2025 · Updated May 15, 2025
CSRF in Jenkins Cadence vManager Plugin 4.0.1-286.v9e25a_740b_a_48 and earlier allows attackers to make Jenkins contact an attacker-specified URL. Form-validation methods accept GET requests and invoke vAPI connection tests with supplied URLs and credentials without enforcing POST. A logged-in victim with Overall/Read permission must be induced to load a crafted request; Jenkins then makes the outbound connection with attacker-chosen credentials.
Summary
What happened
CSRF in Jenkins Cadence vManager Plugin 4.0.1-286.v9e25a_740b_a_48 and earlier allows attackers to make Jenkins contact an attacker-specified URL. Form-validation methods accept GET requests and invoke vAPI connection tests with supplied URLs and credentials without enforcing POST. A logged-in victim with Overall/Read permission must be induced to load a crafted request; Jenkins then makes the outbound connection with attacker-chosen credentials.
The record
- CVE
- CVE-2025-47886
- Published
- May 14, 2025
- Updated
- May 15, 2025
- Vendor
- Jenkins Project
- Product
- Cadence vManager Plugin
- Classifications
- CWE-352, CAPEC-62, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2025CVE publishedPublication date reported by the CVE source.
- May 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.0.1-286.v9e25a_740b_a_48
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo