dbcve.org
Publish To BitbucketApplication · Jenkins

CVE-2025-64149

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to after 0.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a CSRF (Cross-Site Request Forgery) vulnerability in the Jenkins Publish to Bitbucket Plugin versions 0.4 and earlier. The flaw allows authenticated Jenkins users to be tricked into making unintended requests that connect to attacker-controlled URLs using attacker-specified credentials IDs, enabling exfiltration of stored Jenkins credentials.

MitigationUpgrade the Publish to Bitbucket Plugin to version 0.5 or later which addresses the CSRF vulnerability. Additionally, review and rotate any potentially exposed credentials, and implement CSRF protection tokens in Jenkins if not already enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Publish To BitbucketApplication
Affected:<= 0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Publish to Bitbucket Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Publish to Bitbucket' or 'bitbucket' in the list of installed plugins. Alternatively, check the file $JENKINS_HOME/plugins/ for a directory named 'publish-to-bitbucket' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In Jenkins Manage Plugins > Installed tab, locate the Publish to Bitbucket plugin and note the Version column. Alternatively, examine the $JENKINS_HOME/plugins/publish-to-bitbucket/META-INF/MANIFEST.MF file for the Plugin-Version attribute.
    Affected if The version is 0.4 or any version lower than 0.4 (for example, 0.3, 0.2, 0.1)
  3. Verify if the plugin has saved credentials
    Go to Manage Jenkins > Credentials > System > Global credentials and review any stored credentials. Also check the specific job configurations that use the Publish to Bitbucket plugin to see if credentials IDs are referenced.
    Affected if Global or job-level credentials exist and the plugin version is 0.4 or earlier
  4. Check Jenkins global CSRF protection setting
    Go to Manage Jenkins > Configure Global Security > CSRF Protection. Verify whether CSRF protection is enabled or disabled.
    Affected if CSRF protection is disabled and the plugin version is 0.4 or earlier

If the Publish to Bitbucket Plugin is installed at version 0.4 or earlier, the environment is vulnerable to CVE-2025-64149 and the stored Jenkins credentials could be exfiltrated via CSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.4
Interim mitigation

Upgrade the Publish to Bitbucket Plugin to version 0.5 or later which addresses the CSRF vulnerability. Additionally, review and rotate any potentially exposed credentials, and implement CSRF protection tokens in Jenkins if not already enabled.

Fix this in Publish To Bitbucket Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64149 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data