Nexus PlatformApplication · Jenkins
CVE-2023-50766
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Nexus Platform Plugin 3.18.0-03 and earlier allows attackers to send an HTTP request to an attacker-specified URL and parse the response as XML.
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 Nexus Platform Plugin for Jenkins versions 3.18.0-03 and earlier contains a CSRF vulnerability that allows unauthenticated attackers to trick authenticated users into making HTTP requests to attacker-controlled URLs, with the XML response being parsed server-side. This could enable Server-Side Request Forgery (SSRF), potential XXE exploitation if the XML parser is vulnerable, or information disclosure.
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
Nexus PlatformApplication
<= 3.18.0-03CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Verify Nexus Platform Plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Nexus Platform' or 'Nexus IQ' in the list of installed pluginsAffected if The Nexus Platform plugin appears in the installed plugins list
-
Determine installed Nexus Platform Plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Nexus Platform plugin and note the Version column. Alternatively, check the file $JENKINS_HOME/plugins/nexus-*/META-INF/MANIFEST.MF for the Implementation-Version attributeAffected if The installed version is 3.18.0-03 or any earlier version
-
Confirm Jenkins CSRF protection statusGo to Jenkins > Manage Jenkins > Configure Global Security and locate the 'CSRF Protection' section. Verify if Enable proxy compatibility or Crumb API is checked/enabledAffected if CSRF protection is disabled or not properly configured (crumb API not enabled)
-
Check global security configurationGo to Jenkins > Manage Jenkins > Configure Global Security and review the Security Realm and Authorization settings. Ensure standard security practices are in placeAffected if CSRF protection is not explicitly enabled in global security settings
You are affected if the Nexus Platform Plugin is installed at version 3.18.0-03 or earlier AND CSRF protection (crumb API) is not enabled in Jenkins global security settings.
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 Nexus Platform Plugin to version 3.18.0-04 or later. As a general security practice, enable Jenkins crumb API and ensure CSRF protection is enabled in global security settings.
Fix this in Nexus Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50766 — 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-50766 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