Bitbucket Server Integration Plugin allows bypassing CSRF protection for any URLGHSA-qjw6-xvrm-5f2h
HIGHGHSA-qjw6-xvrm-5f2h is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in io.jenkins.plugins:atlassian-bitbucket-server-integration. A fix is available for io.jenkins.plugins:atlassian-bitbucket-server-integration — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-qjw6-xvrm-5f2h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:atlassian-bitbucket-server-integrationReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An extension point in Jenkins allows selectively disabling cross-site request forgery (CSRF) protection for specific URLs. Bitbucket Server Integration Plugin implements this extension point to support OAuth 1.0 authentication.
In Bitbucket Server Integration Plugin 2.1.0 through 4.1.3 (both inclusive) this implementation is too permissive, allowing attackers to craft URLs that would bypass the CSRF protection of any target URL.
Bitbucket Server Integration Plugin 4.1.4 restricts which URLs it disables cross-site request forgery (CSRF) protection for to the URLs that needs it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:atlassian-bitbucket-server-integration | ≥ 2.1.0&&< 4.1.4 | 4.1.4io.jenkins.plugins:atlassian-bitbucket-server-integration:4.1.4 |
Affected Products
bitbucket server integrationjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:atlassian-bitbucket-server-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:atlassian-bitbucket-server-integration to 4.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjw6-xvrm-5f2h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-qjw6-xvrm-5f2h in your dependencies?
Find it across Maven, including transitive dependencies.