ScriptlerApplication · Jenkins
CVE-2021-21668
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 Scriptler Plugin 3.1 and earlier does not escape script content, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Scriptler/Configure permission.
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 Scriptler Plugin 3.1 and earlier does not escape script content when storing or displaying scripts, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers with Scriptler/Configure permission can inject malicious JavaScript that executes in the browsers of other users viewing those 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
ScriptlerApplication
<= 3.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Scriptler Plugin is installedIn Jenkins, navigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins/ directory for the scriptler folderAffected if The Scriptler plugin folder or entry exists in Jenkins plugins
-
Determine installed Scriptler Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and locate Scriptler in the list to view its version, or read the manifest file at $JENKINS_HOME/plugins/scriptler/META-INF/MANIFEST.MFAffected if The version displayed is 3.1 or any version lower than 3.1
-
Check for Scriptler/Configure permission assignmentNavigate to Manage Jenkins > Manage Users > select a user > View Credentials, or check $JENKINS_HOME/users/ directory. In Jenkins, go to Manage Jenkins > Configure Global Security > Authorization to see who has Scriptler/Configure permissionsAffected if Any user account has Scriptler/Configure permission granted to non-admin users
-
Inspect stored Scriptler scripts for suspicious contentNavigate to Manage Jenkins > Scriptler > Scriptler Library, or examine XML files in $JENKINS_HOME/scriptler/ directory for unexpected script tags, eval() calls, or encoded charactersAffected if Any script contains JavaScript code, script tags, event handlers, or unexpected encoded content that could execute in a browser
You are affected if the Scriptler Plugin version is 3.1 or earlier and any user with Scriptler/Configure permission exists in your Jenkins environment.
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 dataUpgrade the Jenkins Scriptler Plugin to version 3.2 or later which properly escapes script content to prevent XSS attacks. Review existing scripts for any malicious content that may have been injected.
Fix this in Scriptler
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-21668 — 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-2021-21668 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