dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2023-25765

CRITICAL · 9.9 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 2.93.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In Jenkins Email Extension Plugin 2.93 and earlier, templates defined inside a folder were not subject to Script Security protection, allowing attackers able to define email templates in folders to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

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 · high confidence

The Jenkins Email Extension Plugin versions 2.93 and earlier has a sandbox bypass vulnerability where templates defined inside folders bypass Script Security protection. An attacker with permission to define email templates in folders can execute arbitrary code in the context of the Jenkins controller JVM.

MitigationUpgrade the Email Extension Plugin to version 2.94 or later which includes the security fix, and review folder-based email templates to ensure they comply with Script Security sandbox rules.

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
Email ExtensionPlugin / extension
Affected:< 2.93.1

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 Email Extension Plugin version
    Go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Email Extension Plugin', or inspect the plugin file at $JENKINS_HOME/plugins/email-ext.jpi for the version manifest
    Affected if The installed version is 2.93 or earlier (below 2.93.1)
  2. Confirm folder plugins are installed
    Check Manage Jenkins > Manage Plugins > Installed for 'CloudBees Folders Plugin' or 'Folders' plugin, or inspect $JENKINS_HOME/plugins for folder-related plugins
    Affected if Any folder management plugin is installed alongside the vulnerable Email Extension version
  3. Identify folders with email templates
    Browse the Jenkins dashboard for folder items (typically with folder icons), then for each folder go to Configure and look for Email Template sections under the Email Extension configuration
    Affected if Any folder contains email template definitions in its configuration
  4. Inspect template contents for script execution
    For each folder-based email template, examine the template content for Groovy scriptlets (syntax like <% %> or ${...}) or references to Script Security-protected APIs
    Affected if Templates in folders contain Groovy scripting or call potentially unsafe methods that would normally require Script Security approval

You are affected if the Email Extension Plugin is version 2.93 or earlier AND folders with email template configurations exist in your Jenkins instance, particularly if those templates contain scripting code.

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.

dbcve · scoped
Upgrade available Upgrade to 2.93.1 or later
Fixed in 2.93.1
Interim mitigation

Upgrade the Email Extension Plugin to version 2.94 or later which includes the security fix, and review folder-based email templates to ensure they comply with Script Security sandbox rules.

Recommended fix High confidence

2.93.1

  1. 1. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab and locate the 'Email Extension Plugin' in the list
  3. 3. Check the current version column to confirm it is below 2.93.1
  4. 4. If an upgrade is available, click the checkbox next to Email Extension Plugin
  5. 5. Click 'Download now and install after restart' button
  6. 6. Wait for the plugin to download and Jenkins to restart
  7. 7. After restart, verify the new version is 2.93.1 or higher under Manage Plugins > Installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Email Extension Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25765 — 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-2023-25765 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