Skip to main content
CVE-2022-41232VulnerabilityPublished Updated

CVE-2022-41232: Jenkins Build-Publisher Plugin · Cross-Site Request Forgery

Affects Jenkins Build-Publisher PluginSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Jenkins project Jenkins Build-Publisher PluginAffected
  • <=1.22
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately update the Jenkins Build-Publisher Plugin to a version that addresses CVE-2022-41232 once available. 2) Implement strict CSRF protection mechanisms on Jenkins instances, including enabling built-in CSRF protection features and validating anti-CSRF tokens on all API endpoints. 3) Restrict access to Jenkins controllers by enforcing network segmentation and limiting access to trusted users and IP addresses only. 4) Monitor Jenkins logs and API usage for suspicious or unexpected requests that could indicate exploitation attempts. 5) Educate users about the risks of social engineering attacks that could trigger CSRF exploits, emphasizing caution when clicking on links or visiting untrusted web pages while authenticated to Jenkins. 6) Regularly back up Jenkins configuration files and job configurations to enable quick restoration in case of tampering or deletion. 7) Review and tighten Jenkins user permissions to follow the principle of least privilege, minimizing the number of users with the ability to modify configurations.

Description

A cross-site request forgery (CSRF) vulnerability in Jenkins Build-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file on the Jenkins controller file system with an empty file by providing a crafted file name to an API endpoint.

References

Community reviews

Loading reviews…