Jenkins Pipeline Aggregator View Plugin vulnerable to Cross-site Scripting

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-28670: 0.46% estimated exploitation activity in the next 30 days; percentile 39.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins 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. Version 1.14 obtains the current URL in a way not susceptible to XSS.

Published by the source

2 Apr 2023, 21:30 UTC

Last modified by the source

7 Apr 2023, 23:03 UTC

Source last checked

26 Oct 2026, 16:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v27q-87jf-j9cr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-28670

Advisory: Jenkins Pipeline Aggregator View Plugin vulnerable to Cross-site Scripting
IDs: CVE-2023-28670, GHSA-v27q-87jf-j9cr
Record: https://patchnext.com/advisories/cve-2023-28670 (revision 1, source checked 26 Oct 2026, 16:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.paul8620.jenkins.plugins:pipeline-aggregator-view 1.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.paul8620.jenkins.plugins:pipeline-aggregator-view: affected < 1.14; fixed in 1.14

## Suggested inspection (read-only)
- Maven com.paul8620.jenkins.plugins:pipeline-aggregator-view: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.paul8620.jenkins.plugins:pipeline-aggregator-view.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v27q-87jf-j9cr (GitHub-reviewed advisory GHSA-v27q-87jf-j9cr lists affected ranges: Maven com.paul8620.jenkins.plugins:pipeline-aggregator-view >=0 <1.14)

Commands are suggestions: review each one before running it.