dbcve.org
Email ExtensionPlugin / extension · Jenkins

CVE-2023-25763

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 various fields included in bundled email templates, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control affected fields.

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

Jenkins Email Extension Plugin versions 2.93 and earlier fail to properly escape content in bundled email template fields, allowing stored XSS attacks when attackers can control these fields. The vulnerability is exploitable through email notifications that render user-controlled data without sanitization.

MitigationUpdate Jenkins Email Extension Plugin to version 2.94 or later where the escaping has been implemented. Review existing email templates and job configurations for any user-controlled fields that could contain malicious scripts.

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. Confirm Email Extension Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory for the email-ext plugin and its version metadata
    Affected if Plugin is present in the Jenkins instance
  2. Check installed version against affected range
    Locate the email-ext plugin version number in the plugin manager UI or plugin metadata files; compare to 2.93.1
    Affected if Version is 2.93 or earlier (less than 2.93.1)
  3. Identify configured email templates
    Inspect the Jenkins configuration directory (typically $JENKINS_HOME) for email template XML/HTML files, or review templates defined in job configurations under the Email Notification or Extended Email Publisher sections
    Affected if Custom email templates exist that may contain user-supplied content
  4. Review jobs using email notifications with user input
    Examine Jenkins jobs that trigger email notifications and accept user-provided parameters, build variables, or external input that could be injected into email subject/body fields
    Affected if Jobs use parameterized content or user-controlled fields in email notification settings

The environment is affected if Jenkins Email Extension Plugin version is 2.93 or earlier AND custom email templates or job configurations contain user-controlled data that gets rendered in email notifications without sanitization.

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 Jenkins Email Extension Plugin to version 2.94 or later where the escaping has been implemented. Review existing email templates and job configurations for any user-controlled fields that could contain malicious scripts.

Recommended fix High confidence

Email Extension Plugin 2.93.1

  1. Navigate to Jenkins Manage Jenkins > Manage Plugins
  2. Select the 'Updates' tab
  3. Locate 'Email Extension Plugin' in the available updates
  4. Select the plugin and choose 'Download now and install after restart'
  5. Wait for the update to download and install
  6. Restart Jenkins to complete the plugin upgrade

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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