JenkinsApplication
CVE-2023-27898
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 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances.
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 fails to escape plugin dependency version strings when rendering plugin incompatibility error messages, allowing stored XSS injection. Attackers who can supply plugins to configured update sites can embed malicious scripts in version fields that execute when administrators view the incompatibility warning.
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
JenkinsApplication
>= 2.270, < 2.394>= 2.277.1, < 2.375.4CVSS 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.
-
Check installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or run 'java -jar jenkins.war --version' from the Jenkins installation directoryAffected if The version is >= 2.270 and < 2.394, OR >= 2.277.1 and < 2.375.4
-
Review update site configurationsNavigate to Manage Jenkins > Manage Plugins > Advanced > Update Sites. Inspect each configured URL for trustworthinessAffected if Untrusted or compromised update sites are configured that accept third-party plugin submissions
-
Check for plugin dependency warnings in logs or UINavigate to Manage Jenkins > Manage Plugins and look for any incompatibility warnings displayed in the UIAffected if Plugin incompatibility warnings are visible and the version falls within affected Jenkins versions
-
Inspect browser console for XSS executionWhile viewing plugin management pages, open browser developer tools and check the console for any unexpected script errors or injected codeAffected if Arbitrary JavaScript executes or error messages contain unsanitized user-controlled input from plugin version fields
A user is affected if their Jenkins version is 2.270 <= version < 2.394 or 2.277.1 <= version < 2.375.4 AND they have configured update sites that could accept plugins with malicious version strings.
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.
dbcve · scoped2.375.42.394
Upgrade Jenkins to a version beyond 2.393 (weekly) or 2.375.3 (LTS) to obtain the patched version; review update site configurations to restrict unauthorized plugin submissions.
Jenkins 2.394+ (weekly) or Jenkins LTS 2.375.4+
- Identify your current Jenkins version in the web UI (Manage Jenkins > About Jenkins) or by running `java -jar jenkins.war --version`
- Backup your Jenkins home directory and configuration before upgrading
- Stop the Jenkins service
- Upgrade Jenkins to version 2.394 or later for the weekly release line, OR upgrade to LTS version 2.375.4 or later
- Restart Jenkins and verify the upgrade was successful by checking the version at Manage Jenkins > About Jenkins
- Verify the fix by ensuring plugin incompatibility error messages no longer execute unsanitized input
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27898 — 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-27898 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