Cross-Site Request Forgery (CSRF) in org.jenkins-ci.main:jenkins-core (CVE-2025-27624)
Summary
Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2025-27624). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.492.2 or later.
Original description
The description as published by the source.
Jenkins 2.499 and earlier, LTS 2.492.1 and earlier does not require POST requests for the HTTP endpoint toggling collapsed/expanded status of sidepanel widgets (e.g., Build Queue and Build Executor Status widgets), resulting in a cross-site request forgery (CSRF) vulnerability.
This vulnerability allows attackers to have users toggle their collapsed/expanded status of sidepanel widgets.
Additionally, as the API accepts any string as the identifier of the panel ID to be toggled, attacker-controlled content can be stored in the victim’s user profile in Jenkins.
Jenkins 2.500, LTS 2.492.2 requires POST requests for the affected HTTP endpoint.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-27624 has been found in org.jenkins-ci.main:jenkins-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.492.2 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2025-27624" on the vendor's site.
CVE-2025-27624 (org.jenkins-ci.main:jenkins-core) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.492.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in org.jenkins-ci.main:jenkins-core.
Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.492.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.jenkins-ci.main:jenkins-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.main:jenkins-core to 2.492.2ステージング環境で 2.492.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web jenkins.io
- web github.com