CVE-2025-64149 json
Jenkins Publish to Bitbucket Plugin vulnerable to CSRF and missing permissions check
published last yr. modified last mo. also GHSA-m244-6mff-p355 , EUVD-2025-36644
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
A cross-site request forgery (CSRF) vulnerability in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Is CVE-2025-64149 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:publish-to-bitbucket | <=0.4 |
no fix listed |
Affected products
- Jenkins Project Jenkins Publish to Bitbucket Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jenkins.io
/security/advisory/2025-10-29/#SECURITY-3576
vendor-advisory, web, third-party-advisory
-
openwall.com
/lists/oss-security/2025/10/29/2
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-64149
advisory
-
github.com
/jenkinsci/publish-to-bitbucket-plugin
package
Sources
- CVE List CVE-2025-64149
- GitHub Advisory GHSA-m244-6mff-p355
- NVD CVE-2025-64149
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.