Extensible Choice ParameterApplication · Jenkins

CVE-2025-64133

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to after 239.v5f5c278708cf or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Extensible Choice Parameter Plugin 239.v5f5c278708cf and earlier allows attackers to execute sandboxed Groovy code.

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

A CSRF vulnerability in the Jenkins Extensible Choice Parameter Plugin (version 239.v5f5c278708cf and earlier) allows remote attackers to trick authenticated users into executing sandboxed Groovy code through forged requests, bypassing intended security restrictions.

MitigationUpdate the Jenkins Extensible Choice Parameter Plugin to the latest version beyond 239.v5f5c278708cf to patch the CSRF vulnerability.

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
Extensible Choice ParameterApplication
Affected:<= 239.v5f5c278708cf

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Verify Extensible Choice Parameter plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI/API to list installed plugins. Search for 'Extensible Choice Parameter' in the plugin list.
    Affected if The plugin is not found in the installed plugins list, meaning the vulnerability does not apply.
  2. Determine the installed version of the plugin
    In the Manage Plugins > Installed tab, locate the Extensible Choice Parameter plugin and note the version number displayed in the 'Version' column.
    Affected if The version number cannot be determined or is not visible in the plugin management interface.
  3. Compare the installed version against the affected range
    Compare the installed version to 239.v5f5c278708cf. Any version less than or equal to 239.v5f5c278708cf is affected.
    Affected if The installed version is 239.v5f5c278708cf or any earlier version (e.g., 238.v..., 237.v..., etc.).
  4. Identify if users have permission to configure the plugin
    Review Jenkins role-based access control (RBAC) or matrix authorization settings to determine which authenticated users can access the Extensible Choice Parameter plugin configuration pages (typically under job parameter configuration).
    Affected if The vulnerability requires an authenticated user with permissions to configure choice parameters; however, the CSRF nature means any authenticated user could be targeted.

You are affected if the Extensible Choice Parameter plugin is installed and its version is 239.v5f5c278708cf or any earlier version.

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 239.v5f5c278708cf
Interim mitigation

Update the Jenkins Extensible Choice Parameter Plugin to the latest version beyond 239.v5f5c278708cf to patch the CSRF vulnerability.

Fix this in Extensible Choice Parameter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-64133 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