GHSA-wv63-gwr9-5c55 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins button labels
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-wv63-gwr9-5c55 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins 2.274 and earlier, LTS 2.263.1 and earlier does not escape button labels in the Jenkins UI.
This results in a cross-site scripting vulnerability exploitable by attackers with the ability to control button labels. An example of buttons with a user-controlled label are the buttons of the Pipeline input step.
Jenkins 2.275, LTS 2.263.2 escapes button labels in the Jenkins UI.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.275org.jenkins-ci.main:jenkins-core:2.275 |
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.263.2&&< 2.275 | 2.275org.jenkins-ci.main:jenkins-core:2.275 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.275 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wv63-gwr9-5c55 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wv63-gwr9-5c55 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-wv63-gwr9-5c55. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-0:2.263.3.1612433584-1.el7 | RHSA-2021:0637 |
| Red Hat OpenShift Container Platform 4.5 | conmon-2:2.0.21-1.rhaos4.5.el7 | RHSA-2021:0429 |
| Red Hat OpenShift Container Platform 4.6 | jenkins-0:2.263.3.1612434510-1.el8 | RHSA-2021:0423 |
| Red Hat OpenShift Container Platform 4.8 | atomic-openshift-service-idler-0:4.8.0-202106281541.p0.git.39cfc66.assembly.stream.el8 | RHSA-2021:2437 |
Frequently Asked Questions
Is GHSA-wv63-gwr9-5c55 in your dependencies?
O3 Security finds GHSA-wv63-gwr9-5c55 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.