ScriptlerApplication · Jenkins
CVE-2021-21700
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.3 and earlier does not escape the name of scripts on the UI when asking to confirm their deletion, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by exploitable by attackers able to create Scriptler scripts.
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 confidenceStored XSS vulnerability in Jenkins Scriptler Plugin where the script name parameter is not escaped when rendered in the deletion confirmation UI. An authenticated attacker with Scriptler script creation privileges can embed malicious JavaScript in a script name; when an administrator views the deletion confirmation, the script executes in their browser.
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.3CVSS 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.
-
Confirm Scriptler Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Scriptler' in the list, or check the file system at $JENKINS_HOME/plugins for the scriptler directoryAffected if Scriptler Plugin is not found in the installed plugins list
-
Identify Scriptler Plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate Scriptler and note the Version column; alternatively, read the manifest file at $JENKINS_HOME/plugins/scriptler/META-INF/MANIFEST.MFAffected if The version is 3.3 or lower (or unable to determine version)
-
Check for Scriptler script creation permissionsNavigate to Manage Jenkins > Manage and Assign Roles > Assign Roles, or check $JENKINS_HOME/users/ for user configuration files. Review whether any users or groups have the 'Scriptler: Create Script' permission enabledAffected if Any user or group has Scriptler script creation privileges (indicates potential attack vector)
-
Review existing Scriptler scripts for suspicious namesNavigate to Manage Jenkins > Scriptler > Scripts and inspect each script's name field for unusual characters such as <script>, javascript:, or HTML tags that could indicate injected XSS payloadsAffected if Any script name contains HTML/JavaScript tags or appears designed to execute code
The environment is affected if the Scriptler Plugin is installed with version 3.3 or lower AND any user has Scriptler script creation privileges, since the XSS executes when an administrator deletes a maliciously-named script.
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 Scriptler Plugin to version 3.4 or later which properly escapes the script name. As a compensating control, restrict Scriptler script creation permissions to trusted users only until patching is complete.
Fix this in Scriptler
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21700 — 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-21700 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