Skip to main content
CVE-2022-41227VulnerabilityPublished Updated

CVE-2022-41227: Jenkins NS-ND Integration Performance Publisher Plugin · Cross-Site Request Forgery

Affects Jenkins NS-ND Integration Performance Publisher PluginSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.8High
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:N/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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Jenkins project Jenkins NS-ND Integration Performance Publisher PluginAffected
  • <=4.8.0.129
Fixed in–

AI-suggested

1. Immediately update the Jenkins NS-ND Integration Performance Publisher Plugin to the latest version once a patch is released by the Jenkins project. 2. Until a patch is available, restrict access to Jenkins instances to trusted networks and users only, using network segmentation and VPNs. 3. Implement strict Content Security Policy (CSP) and SameSite cookie attributes to help mitigate CSRF risks. 4. Educate Jenkins users about the risks of clicking on untrusted links or visiting suspicious websites while authenticated to Jenkins. 5. Enable and enforce Jenkins security best practices such as CSRF protection settings, user authentication, and role-based access control (RBAC). 6. Monitor Jenkins logs and network traffic for unusual outbound connections to unknown servers, which could indicate exploitation attempts. 7. Consider using web application firewalls (WAFs) that can detect and block CSRF attack patterns targeting Jenkins. 8. Review and audit Jenkins plugin usage regularly to minimize the attack surface by removing unnecessary or outdated plugins.

Description

A cross-site request forgery (CSRF) vulnerability in Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.129 and earlier allows attackers to connect to an attacker-specified webserver using attacker-specified credentials.

References

Community reviews

Loading reviews…