Skip to content
Fencer Vulns
medium 5.4

CVE-2022-27196 json

Stored Cross-site Scripting vulnerability in Jenkins Favorite Plugin

published 2022-03-15 4 y ago modified 2026-06-17 4 mo ago also GHSA-874r-46c6-7p4r , EUVD-2022-1372

cvss
5.4
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 57%
public exploits
0
none known

Summary

Jenkins Favorite Plugin 2.4.0 and earlier does not escape the names of jobs in the favorite column, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure or Item/Create permissions.

Patch / fix

  • maven org.jvnet.hudson.plugins:favorite 2.4.1
  • Jenkins project Jenkins Favorite Plugin 2.3.3.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-27196 updated cvss 3.5

jenkins-2-plugins/favorite: Favorite Plugin XSS Vulnerability

  • Red Hat OpenShift Container Platform 4 jenkins-2-plugins
    affected: no fix available
  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/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 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.jvnet.hudson.plugins:favorite
<2.4.1
2.4.1

Affected products

  • Jenkins project Jenkins Favorite Plugin

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns 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.