CVE-2022-27207 json
Stored Cross-site Scripting vulnerability in Jenkins global-build-stats Plugin
published 4y ago modified 4mo ago also GHSA-wj78-8xrx-phr7 , EUVD-2022-1569
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Jenkins global-build-stats Plugin 1.5 and earlier does not escape multiple fields in the chart configuration on the 'Global Build Stats' page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Overall/Administer permission.
Patch / fix
Is CVE-2022-27207 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:global-build-stats | <=1.5 |
no fix listed |
Affected products
- Jenkins project Jenkins global-build-stats Plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/jenkinsci/global-build-stats-plugin/commit/214f74360b3a91734b6e2a4b281ff0086a1e0679
web
-
jenkins.io
/security/advisory/2022-03-15/#SECURITY-1886
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/03/15/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-27207
advisory
-
github.com
/jenkinsci/global-build-stats-plugin
package
Sources
- CVE List CVE-2022-27207
- GitHub Advisory GHSA-wj78-8xrx-phr7
- NVD CVE-2022-27207
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.