CVE-2024-28153: Jenkins OWASP Dependency-Check Plugin Stored XSS Vulnerability

Summary

06/03/2024
Yes i
Moderate
5.4

CVE-2024-28153: Jenkins OWASP Dependency-Check Plugin has stored XSS vulnerability. Affects org.jenkins-ci.plugins:dependency-check-jenkins-plugin versions < 5.4.6. Fixed in 5.4.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Jenkins OWASP Dependency-Check Plugin is a Maven ecosystem package that provides vulnerability scanning capabilities for Jenkins. It analyzes project dependencies and generates reports to identify potential security issues. The plugin helps developers ensure that their projects do not include vulnerable components.

Vulnerability Detail

The plugin version 5.4.5 and earlier are affected by a stored cross-site scripting (XSS) vulnerability. This vulnerability arises due to the plugin's failure to properly escape vulnerability metadata from Dependency-Check reports. An attacker can exploit this vulnerability by injecting malicious code into the vulnerability metadata, which will be executed when the report is viewed. This can lead to unauthorized access, data theft, or other malicious activities.

How To Fix

Latest published version: 5.6.5 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.4.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update the plugin to the fixed version as soon as possible.

Conclusion

The Jenkins OWASP Dependency-Check Plugin version 5.4.5 and earlier are vulnerable to a stored XSS attack. It is crucial to update the plugin to version 5.4.6 or later to mitigate the risk associated with this vulnerability. Failure to do so may result in unauthorized access, data theft, or other malicious activities. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:dependency-check-jenkins-plugin →

Share this vulnerability

FAQ

The stored XSS vulnerability in the Jenkins OWASP Dependency-Check Plugin can allow an attacker to execute arbitrary code within the context of the affected user's browser. This can lead to unauthorized access, data theft, or other malicious activities.

You can use Vulert's playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file.

At the time of this advisory, there are no known public exploits specifically targeting this vulnerability. However, it is crucial to update the plugin to the fixed version to prevent potential exploitation.

No, updating the plugin to the fixed version is the only recommended solution to mitigate the risk associated with this vulnerability. It ensures that the vulnerability metadata is properly escaped and prevents XSS attacks.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:dependency-check-jenkins-plugin.

How To Fix

Latest published version: 5.6.5 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.4.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback