Rich Text PublisherApplication · Jenkins
CVE-2022-34786
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 Rich Text Publisher Plugin 1.4 and earlier does not escape the HTML message set by its post-build step, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure jobs.
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 Rich Text Publisher Plugin versions 1.4 and earlier fail to escape HTML content in messages configured through its post-build step. This allows authenticated users with job configuration permissions to inject malicious scripts that persist and execute when other users view the build output.
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
Rich Text PublisherApplication
<= 1.4CVSS 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.
-
Verify Rich Text Publisher Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or check the plugins directory (typically $JENKINS_HOME/plugins/) for the rich-text-publisher-plugin folderAffected if The plugin folder exists or the plugin appears in the installed list
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find 'Rich Text Publisher' and note the version number; or check the version file in $JENKINS_HOME/plugins/rich-text-publisher-plugin/META-INF/MANIFEST.MFAffected if The version is 1.4 or earlier (e.g., 1.4, 1.3, 1.2, etc.)
-
Identify post-build steps using the pluginNavigate to job configuration pages (or inspect config.xml files in $JENKINS_HOME/jobs/) and look for <publishRichTextPublisher> or similar XML elements under the <publishers> sectionAffected if A post-build step referencing Rich Text Publisher is configured for any job
-
Review job configuration permissionsNavigate to Manage Jenkins > Manage and Assign Roles, or check the authorization matrix in Configure Global Security, to identify which users or groups have Job/Configure permissionsAffected if Users with Job/Configure permission include untrusted or anonymous accounts (this indicates potential attack surface for CVE-2022-34786)
You are affected if the Rich Text Publisher Plugin version is 1.4 or earlier AND a post-build step using this plugin is configured in at least one job, especially if untrusted users have job configuration permissions.
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 to a patched version of the Rich Text Publisher Plugin that properly escapes HTML output, or limit job configuration permissions to trusted users until the patch is applied.
Fix this in Rich Text Publisher
Scoped from the published advisory
- Consultation3.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34786 — 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-34786 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