dbcve.org
Loadcomplete SupportApplication · Jenkins

CVE-2023-33007

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 LoadComplete support Plugin 1.0 and earlier does not escape the LoadComplete test name, 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 confidence

The Jenkins LoadComplete support Plugin 1.0 and earlier fails to escape the LoadComplete test name field before rendering it in the web interface. This allows an authenticated attacker with Item/Configure permission to inject malicious JavaScript code into the test name, which executes in the browsers of other users viewing the affected page (stored XSS).

MitigationUpgrade to a patched version of the LoadComplete support Plugin if available. If no patch exists, implement output encoding for the test name field before rendering or disable the plugin until a fix is released.

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
Loadcomplete SupportApplication
Affected:<= 1.0

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
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 checks

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

  1. Verify if LoadComplete Support plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins. Click on the 'Installed' tab and search for 'LoadComplete' or 'Loadcomplete Support' in the list of installed plugins.
    Affected if The plugin appears in the Installed plugins list.
  2. Confirm the plugin version
    In the Installed plugins tab, locate the LoadComplete Support plugin and check the Version column. The vulnerability affects version 1.0 and earlier.
    Affected if The Version listed is 1.0 or lower.
  3. Identify jobs using the LoadComplete plugin
    Navigate to Jenkins > Manage Jenkins > System Configuration > LoadComplete (or check individual job configurations). Review each job to see if the LoadComplete plugin is configured and being used.
    Affected if Any job has LoadComplete plugin configuration enabled.
  4. Inspect the test name field in job configurations
    For each job configured with LoadComplete, go to Job > Configure and locate the LoadComplete test name field. View the page source or inspect the HTML to check if the test name value is properly escaped (look for HTML encoding like &lt; &gt; &quot;).
    Affected if The test name field displays raw unescaped characters or contains user-supplied input without proper HTML encoding.

You are affected if the LoadComplete Support plugin is installed at version 1.0 or earlier and is configured in any Jenkins jobs, as the unescaped test name field creates a stored XSS vulnerability.

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 a release after 1.0
Interim mitigation

Upgrade to a patched version of the LoadComplete support Plugin if available. If no patch exists, implement output encoding for the test name field before rendering or disable the plugin until a fix is released.

Recommended fix Moderate confidence

Update to the latest version of LoadComplete support plugin available in the Jenkins plugin repository (version higher than 1.0)

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Locate the LoadComplete support plugin in the Installed tab
  3. Check for available updates for the LoadComplete support plugin
  4. If an update is available, select the plugin and click 'Download now and install after restart' or 'Update'
  5. Alternatively, download the newer plugin .jpi file from the Jenkins plugin repository and upload it via 'Advanced' tab > 'Upload Plugin'
  6. After installation, restart Jenkins if required

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

Fix this in Loadcomplete Support Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33007 — 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-2023-33007 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