JenkinsApplication
CVE-2025-27624
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 2.499 and earlier, LTS 2.492.1 and earlier allows attackers to have users toggle their collapsed/expanded status of sidepanel widgets (e.g., Build Queue and Build Executor Status widgets).
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins 2.499 and earlier, and LTS 2.492.1 and earlier allows authenticated users to be tricked into toggling the collapsed/expanded status of sidepanel widgets (Build Queue and Build Executor Status) via malicious requests.
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.492.2< 2.500CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 your Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /api/json?tree=version to retrieve the installed version numberAffected if The version is less than 2.492.2 or is between 2.492.2 and 2.499 (inclusive)
-
Confirm Jenkins security is enabledGo to Manage Jenkins > Security and verify that Enable security is checked, or check config.xml for <useSecurity>true</useSecurity>Affected if Security is enabled (this is required for the CSRF to be exploitable - the attacker needs a valid authenticated session)
-
Verify sidepanel widgets are accessibleLog in as any user and navigate to the main Jenkins dashboard. Look for the Build Queue and Build Executor Status widgets in the left sidepanelAffected if These widgets are present and can be toggled (they are enabled by default)
-
Check if multiple users existGo to Manage Jenkins > Users to see if more than one user account exists, or check if any form of authentication is required to access JenkinsAffected if Multiple authenticated users exist or the instance uses external authentication (LDAP, etc.), increasing the attack surface
You are affected if your Jenkins version is below 2.492.2 or between 2.492.2 and 2.499 inclusive, security is enabled, and authenticated users can access the dashboard with sidepanel widgets present.
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.492.22.500
Upgrade to Jenkins 2.499.1 or LTS 2.492.2 or later to obtain the security fix.
Jenkins LTS 2.492.2 or later; Jenkins 2.500 or later
- Schedule a maintenance window and notify users
- Backup your Jenkins home directory and any critical configurations
- Review installed plugins for compatibility with Jenkins 2.492.2+ or 2.500+
- Download the new Jenkins WAR file (LTS 2.492.2 or weekly 2.500) from https://www.jenkins.io/download/
- Stop the Jenkins service
- Replace the existing jenkins.war file in your Jenkins installation directory
- Start the Jenkins service
- Log in and verify the sidepanel widgets (Build Queue, Build Executor Status) are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27624 — 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-2025-27624 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