dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-39423

HIGH · 7.1 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in Jenst Add to Header add-to-header allows Stored XSS.This issue affects Add to Header: from n/a through <= 1.0.

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

The Jenkin Add to Header plugin <= 1.0 contains a CSRF vulnerability that enables attackers to inject malicious JavaScript through stored XSS. By tricking an authenticated administrator into visiting a crafted page, attackers can force the admin's browser to submit requests that inject XSS payloads into the plugin's settings, which then execute whenever administrators view the affected header configuration pages.

MitigationAdd CSRF nonces to all form submissions in the plugin and validate them server-side; implement proper input sanitization and output encoding for the Add to Header functionality to prevent stored XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 Add to Header plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'add-to-header') println it.displayName + ': ' + it.version }
    Affected if The plugin appears in the list of installed plugins
  2. Confirm plugin version is <= 1.0
    Compare the installed version from step 1 to the affected version range <= 1.0
    Affected if Installed version is 1.0 or lower, or version cannot be determined (assumed vulnerable)
  3. Access the plugin configuration page
    Navigate to Manage Jenkins > Configure System and look for the 'Add to Header' section, or attempt direct access to the configuration URL if known
    Affected if The configuration page is accessible and allows saving header settings
  4. Check if CSRF protection is missing on form submissions
    Use the Jenkins script console to inspect the plugin's form submissions for CSRF tokens: Jenkins.instance.getExtensionList('add.to.header.SomeExtension') or examine the plugin's .hpi file for missing crumb (CSRF) validation in form submission handlers
    Affected if No CSRF crumb token validation is found in the plugin's form handling code

If the Add to Header plugin is installed at version 1.0 or lower, the environment is affected by this CSRF-to-stored-XSS vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add CSRF nonces to all form submissions in the plugin and validate them server-side; implement proper input sanitization and output encoding for the Add to Header functionality to prevent stored XSS execution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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