dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2023-25764

MEDIUM · 5.4 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 2.93.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins Email Extension Plugin 2.93 and earlier does not escape, sanitize, or sandbox rendered email template output or log output generated during template rendering, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create or change custom email templates.

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 fails to properly escape, sanitize, or sandbox email template output and log output generated during template rendering. This allows stored XSS attacks where malicious scripts can be injected through custom email templates and executed when recipients view the rendered emails.

MitigationUpdate the Email Extension Plugin to version 2.94 or later which implements proper output encoding. Additionally, restrict permissions for who can create or modify custom email templates to reduce the attack surface.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Verify Email Extension Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Email Extension Plugin', or inspect $JENKINS_HOME/plugins/email-ext/ for the plugin directory.
    Affected if The plugin is not installed or the directory does not exist means not affected via this vector.
  2. Check the installed Email Extension Plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab > Email Extension Plugin and note the version number. Alternatively, inspect the plugin's manifest file at $JENKINS_HOME/plugins/email-ext/META-INF/MANIFEST.MF for the Implementation-Version.
    Affected if Version is 2.93 or earlier, or the version starts with a number less than 2.93.1.
  3. Identify if custom email templates exist
    Check for custom email templates in the Jenkins controller's file system at $JENKINS_HOME/email-ext/ or subdirectories under it. Also check project job configurations for custom templates configured via the Extended Email Publisher plugin.
    Affected if Custom email templates are present and actively used by jobs or the default configuration.
  4. Verify template rendering is in use
    Review Jenkins jobs that use the Extended Email Publisher post-build action and check if custom email templates are referenced in the 'Template' or 'Default Template' fields in job configurations.
    Affected if Jobs are configured to use custom or default email templates that could render user-controlled content.

A user is affected if they have Email Extension Plugin version 2.93 or earlier installed AND they use custom email templates that can be viewed by recipients, allowing injected scripts to execute in email clients.

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

Update the Email Extension Plugin to version 2.94 or later which implements proper output encoding. Additionally, restrict permissions for who can create or modify custom email templates to reduce the attack surface.

Recommended fix High confidence

2.93.1

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Go to the 'Available' tab and search for 'Email Extension Plugin'
  3. Locate the Email Extension Plugin and update to version 2.93.1
  4. Alternatively, navigate to the 'Updates' tab to find the available update for Email Extension Plugin and update to version 2.93.1
  5. After the update completes, restart Jenkins if required to apply the changes
  6. Verify the plugin version is showing 2.93.1 or later in the 'Installed' tab

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

Fix this in Email Extension Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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