Performance PublisherApplication · Jenkins
CVE-2023-28682
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 Performance Publisher Plugin 8.09 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 Performance Publisher Plugin versions 8.09 and earlier contains an XML External Entity (XXE) vulnerability because its XML parser is not configured to disable external entity processing. This allows attackers to inject malicious XML payloads that could lead to data exfiltration, denial of service, or server-side request forgery.
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
Performance PublisherApplication
<= 8.09CVSS 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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Check installed Performance Publisher plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, search for 'Performance Publisher', and note the version listed. Alternatively, examine the plugin's manifest file (JENKINS_HOME/plugins/performance.jpi or performance/WEB-INF/MANIFEST.MF) for the Version attribute.Affected if The installed version is 8.09 or earlier.
-
Confirm plugin is installed and activeIn Jenkins, verify the Performance Publisher plugin appears in Manage Jenkins > Manage Plugins > Installed and is marked as 'Enabled' or 'Active'. Check that the 'Performance' build step or post-build action is available when configuring a job.Affected if The plugin is installed and active.
-
Identify users with permission to run performance reportsNavigate to the job configuration of a project using Performance Publisher, or check Manage Jenkins > Manage and Assign Roles to see which users or groups have permission to configure builds or publish performance test results.Affected if Users other than trusted administrators can configure or trigger performance report publishing.
-
Verify XML-based report input is acceptedCheck the job configuration for Performance Publisher: look for report formats that accept XML input (such as JMeter XML, JUnit XML, or other XML-based performance test results) and confirm these are enabled or can be specified by job configurators.Affected if The plugin is configured to accept XML-based performance reports as input.
A user is affected if the Performance Publisher plugin version is 8.09 or earlier AND untrusted users can submit or configure XML-based performance test reports in Jenkins.
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 Jenkins Performance Publisher Plugin to version 8.10 or later, which properly configures the XML parser to prevent XXE attacks. If unable to upgrade immediately, restrict plugin access to trusted users only.
Fix this in Performance Publisher
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28682 — 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-2023-28682 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