CVE-2023-28670
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 Pipeline Aggregator View Plugin 1.13 and earlier does not escape a variable representing the current view's URL in inline JavaScript, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by authenticated attackers with Overall/Read 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 Pipeline Aggregator View Plugin versions 1.13 and earlier contains a stored cross-site scripting (XSS) vulnerability where a variable representing the current view's URL is not escaped before being used in inline JavaScript, allowing authenticated attackers with Overall/Read permission to inject malicious 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<= 1.13CVSS 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 Pipeline Aggregator View Plugin is installedRun the following in the Jenkins Script Console: Jenkins.instance.pluginManager.plugins.find{it.shortName == 'pipeline-aggregator-view'}?.displayNameAffected if The plugin name appears in the output, indicating it is installed
-
Check installed plugin versionRun the following in the Jenkins Script Console: Jenkins.instance.pluginManager.plugins.find{it.shortName == 'pipeline-aggregator-view'}?.versionAffected if The version returned is 1.13 or lower (or the version cannot be determined, meaning it is an unpatched release)
-
Verify Overall/Read permission is activeNavigate to Manage Jenkins > Manage Users and verify if any users or groups have Overall/Read permission; alternatively, check if anonymous read access is enabled under Manage Jenkins > Configure Global SecurityAffected if Overall/Read permission is granted to any user or group (this is the default for authenticated users, and anonymous read access is often enabled)
If the Pipeline Aggregator View Plugin version is 1.13 or earlier and Overall/Read permission is granted to any user (including authenticated or anonymous users), the environment is vulnerable to stored XSS via CVE-2023-28670.
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.
dbcve · scopedUpdate the Jenkins Pipeline Aggregator View Plugin to version 1.14 or later which properly escapes the URL variable; alternatively, restrict Overall/Read permission to trusted users until the patch can be applied.
Pipeline Aggregator View plugin version 1.14 or later
- 1. In the Jenkins web UI, navigate to 'Manage Jenkins'
- 2. Click on 'Manage Plugins'
- 3. Go to the 'Installed' tab
- 4. Search for 'Pipeline Aggregator View' in the plugin list
- 5. If the plugin is installed, check for updates or directly update to the latest version
- 6. Alternatively, if updates are not showing, download the fixed version (1.14 or later) from the Jenkins plugin repository and install it manually via 'Advanced' > 'Upload Plugin'
- 7. After upgrade, restart Jenkins if required
- 8. Verify the plugin is now running at version 1.14 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28670 — 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-2023-28670 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