Update Center2Application · Jenkins
CVE-2023-27905
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 update-center2 3.13 and 3.14 renders the required Jenkins core version on plugin download index pages without sanitization, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide a plugin for hosting.
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 confidenceJenkins update-center2 versions 3.13 and 3.14 contain a stored XSS vulnerability where the required Jenkins core version field on plugin download index pages is rendered without sanitization. Attackers with the ability to provide plugins for hosting can inject malicious JavaScript into the core version value, which executes when users view the plugin download pages.
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
Update Center2Application
= 3.13= 3.14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
-
Identify update-center2 versionLocate the update-center2 installation or package and check its version (e.g., check package.json, VERSION file, or git tags if built from source). Compare against affected versions 3.13 and 3.14.Affected if The installed version is 3.13 or 3.14
-
Confirm custom update center is in useCheck if Jenkins is configured to use a custom update center URL (look for update-center.url in Jenkins configuration or custom uc.*.url properties).Affected if A custom update center pointing to the affected update-center2 instance is configured
-
Check for user-provided plugin hostingDetermine if the update center accepts plugin uploads or hosting from external users. Review the update-center2 configuration for plugin submission or hosting features.Affected if Users can submit or upload plugins to the update center without strict metadata validation
-
Inspect plugin index for unsanitized contentExamine generated plugin index files (JSON files in the update center's download directory) for the 'requiredCore' field or core version values. Look for unexpected characters, script tags, or encoded payloads.Affected if Plugin metadata contains unsanitized JavaScript in core version fields (e.g., <script> tags, event handlers)
A user is affected if they run update-center2 version 3.13 or 3.14 AND use it to serve plugins from untrusted sources, or if their Jenkins instance loads a custom update center generated by these versions.
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 dataImplement proper output encoding/sanitization when rendering the Jenkins core version field on plugin download pages. Additionally, validate and sanitize all plugin metadata before it is rendered in the index.
Fix this in Update Center2
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27905 — 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-27905 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