dbcve.org
DingtalkApplication · Jenkins

CVE-2025-47888

MEDIUM · 5.9 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to after 2.7.3 or later.
See remediation →
65/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
Jenkins DingTalk Plugin 2.7.3 and earlier unconditionally disables SSL/TLS certificate and hostname validation for connections to the configured DingTalk webhooks.

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 DingTalk Plugin unconditionally disables SSL/TLS certificate and hostname validation for connections to configured DingTalk webhooks, allowing man-in-the-middle attackers to intercept credentials and messages sent to the webhook endpoint.

MitigationUpgrade to Jenkins DingTalk Plugin version 2.7.4 or later, which restores proper SSL/TLS certificate and hostname validation for webhook connections.

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
DingtalkApplication
Affected:<= 2.7.3

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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. Check installed DingTalk plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, search for 'DingTalk' and note the version number in the 'Version' column
    Affected if Version is 2.7.3 or lower
  2. Verify plugin is configured with a webhook
    Navigate to Jenkins > Manage Jenkins > Configure System > DingTalk section, check if any webhook URLs are configured under the 'Webhooks' or similar configuration area
    Affected if A webhook URL is configured (vulnerability only applies when plugin is actively used with DingTalk)
  3. Confirm SSL/TLS validation is disabled
    If available, inspect the plugin configuration for any 'Trust all certificates' or 'Disable SSL verification' option that is checked/enabled, or examine plugin configuration XML files in JENKINS_HOME if accessible
    Affected if SSL/TLS certificate/hostname validation is explicitly disabled or unconditionally bypassed in the configuration

User is affected if Jenkins DingTalk Plugin version 2.7.3 or lower is installed AND the plugin is configured with a DingTalk webhook URL for sending notifications

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 2.7.3
Interim mitigation

Upgrade to Jenkins DingTalk Plugin version 2.7.4 or later, which restores proper SSL/TLS certificate and hostname validation for webhook connections.

Fix this in Dingtalk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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