AnchorchainApplication · Jenkins
CVE-2025-30196
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 · uneditedJenkins AnchorChain Plugin 1.0 does not limit URL schemes for links it creates based on workspace content, allowing the `javascript:` scheme, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control the input file for the Anchor Chain post-build step.
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 confidenceThe Jenkins AnchorChain Plugin 1.0 does not validate URL schemes when generating links from workspace content, permitting the javascript: scheme. This allows attackers who control the input file for the Anchor Chain post-build step to inject malicious scripts that execute when users view the generated links, resulting in stored XSS.
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
AnchorchainApplication
= 1.0CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify AnchorChain plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'AnchorChain' in the list of installed pluginsAffected if The AnchorChain plugin appears in the installed plugins list with version 1.0
-
Confirm the exact plugin versionIn the Installed Plugins list, locate the AnchorChain plugin and note the Version column; the affected version is 1.0Affected if The version column shows exactly 1.0 (no patch version indicated)
-
Check for Anchor Chain post-build action usageNavigate to a job configuration page, scroll to the 'Post-build Actions' section, and look for 'Anchor Chain' in the dropdown menuAffected if Anchor Chain is listed as an available post-build action and is configured for any job
-
Inspect workspace for anchor chain input filesNavigate to a completed build > Workspace, and look for files that may contain URL-like content (common patterns: .txt, .xml, or generated report files containing hyperlinks)Affected if Workspace contains files with URL patterns that could be processed by the Anchor Chain plugin
-
Verify plugin is enabledGo to Manage Jenkins > Manage Plugins > Installed, find AnchorChain, and confirm the 'Enabled' checkbox is checked, or check Manage Nodes > Configure > Agents for any disabled stateAffected if The AnchorChain plugin is enabled and not explicitly disabled
You are affected if the AnchorChain plugin version 1.0 is installed, enabled, and configured as a post-build action that processes workspace content containing URLs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the AnchorChain plugin that implements strict allowlist validation for URL schemes, rejecting javascript: and other dangerous schemes; alternatively, disable the plugin until a fix is available.
Fix this in Anchorchain
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-30196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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