Extreme Feedback PanelApplication · Jenkins
CVE-2022-34790
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 eXtreme Feedback Panel Plugin 2.0.1 and earlier does not escape the job names used in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure 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 eXtreme Feedback Panel Plugin version 2.0.1 and earlier fails to properly escape job names before rendering them in HTML tooltips. This allows an attacker with Item/Configure permission to inject malicious JavaScript code into job names, which executes when other users view these tooltips.
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
Extreme Feedback PanelApplication
<= 2.0.1CVSS 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.
-
Locate the Extreme Feedback Panel plugin fileBrowse the Jenkins plugins directory (typically $JENKINS_HOME/plugins) and look for a file named 'extreme-feedback-panel.jpi' or 'extreme-feedback-panel.hpi'. If the file exists, the plugin is installed.Affected if The plugin file exists in the plugins directory.
-
Determine the installed plugin versionExtract the MANIFEST.MF file from the plugin .jpi/.hpi (which is a ZIP archive) and read the 'Implementation-Version' or 'Plugin-Version' attribute. Alternatively, navigate to Manage Jenkins > Manage Plugins > Installed and locate 'Extreme Feedback Panel' to see its version.Affected if The version is 2.0.1 or earlier.
-
Verify if Item/Configure permission is broadly grantedNavigate to Manage Jenkins > Manage Users > click on a user > click 'Configure' to view their permissions. Or review the authorization matrix (Manage Jenkins > Global Security > Authorization). Check if users other than administrators have the 'Item/Configure' permission.Affected if Non-admin users have Item/Configure permission, allowing them to modify job names.
-
Inspect job names for potential injection payloadsNavigate to the Jenkins dashboard and review the list of job names. Look for job names containing HTML tags, JavaScript code (such as <script>, javascript:, onerror=, onload=), or unusual character sequences that may indicate injected payloads.Affected if Any job name contains HTML or JavaScript code that could execute in a tooltip.
You are affected if the Extreme Feedback Panel plugin (version 2.0.1 or earlier) is installed AND users with Item/Configure permission exist in your environment.
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.
From vendor dataUpgrade the plugin to version 2.0.2 or later which properly escapes job names in tooltips. As a workaround, restrict Item/Configure permission to trusted users only.
Fix this in Extreme Feedback Panel
Scoped from the published advisory
- Consultation1.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34790 — 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-2022-34790 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