dbcve.org
Html PublisherApplication · Jenkins

CVE-2024-28149

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to 1.32.1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Jenkins HTML Publisher Plugin 1.16 through 1.32 (both inclusive) does not properly sanitize input, allowing attackers with Item/Configure permission to implement cross-site scripting (XSS) attacks and to determine whether a path on the Jenkins controller file system exists.

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 · moderate confidence

Jenkins HTML Publisher Plugin versions 1.16-1.32 fail to properly sanitize user-supplied input in the plugin's configuration. This allows authenticated attackers with Item/Configure permission to inject malicious scripts (XSS) into rendered pages and to probe the Jenkins controller file system to determine whether specific paths exist, potentially revealing sensitive directory structures.

MitigationUpgrade the HTML Publisher Plugin to version 1.33 or later which contains proper input sanitization. Before upgrading in production, test the new version in a non-production Jenkins environment to verify compatibility with existing jobs and configurations.

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
Html PublisherApplication
Affected:>= 1.16, < 1.32.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check HTML Publisher Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: `java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep html`
    Affected if The installed version is 1.16 through 1.32.0 (anything >=1.16 but <1.32.1)
  2. Verify plugin is in use
    Search job configurations for 'htmlpublisher' or look for Publish HTML reports post-build actions in existing jobs
    Affected if Jobs are configured to publish HTML reports using this plugin, exposing the vulnerability surface
  3. Check for users with Item/Configure permission
    Review Jenkins authorization matrix or folder-based permissions at Manage Jenkins > Manage Users and in folder configurations
    Affected if Any user or group has Item/Configure permission on the jobs using HTML Publisher, allowing them to trigger the XSS and path probing
  4. Inspect plugin configuration entries
    Review job config.xml files or view job configuration pages that contain HTML Publisher settings, looking for report directory and file patterns
    Affected if HTML report publishing is configured with user-influenced paths that could be manipulated for the path existence probe

You are affected if the HTML Publisher Plugin version is 1.16 through 1.32.0 AND the plugin is configured in any job AND attackers can obtain Item/Configure permission on those jobs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.32.1 or later
Fixed in 1.32.1
Interim mitigation

Upgrade the HTML Publisher Plugin to version 1.33 or later which contains proper input sanitization. Before upgrading in production, test the new version in a non-production Jenkins environment to verify compatibility with existing jobs and configurations.

Recommended fix High confidence

1.32.1

  1. Identify all Jenkins instances with HTML Publisher Plugin versions 1.16 through 1.32 installed
  2. Access the Manage Plugins page in Jenkins (Manage Jenkins > Manage Plugins)
  3. Locate the HTML Publisher plugin in the Installed tab
  4. If an affected version is found, check for updates in the Updates tab
  5. Upgrade HTML Publisher Plugin to version 1.32.1 or later
  6. Restart Jenkins if required to complete the plugin update
  7. Verify the upgrade was successful by checking the plugin version in Manage Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Html Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28149 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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