CVE-2022-41253: Jenkins CONS3RT Plugin · Cross-Site Request Forgery
Affects Jenkins CONS3RT PluginSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins project Jenkins CONS3RT Plugin | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation involves disabling the Jenkins CONS3RT Plugin if it is not essential to operations until a security patch is released. 2. Restrict access to Jenkins instances to trusted networks and users, implementing network segmentation and firewall rules to limit exposure. 3. Enforce strict user authentication and authorization policies within Jenkins, ensuring that only necessary users have access to sensitive plugins and credentials. 4. Monitor Jenkins logs and network traffic for unusual outbound connections, especially to unknown HTTP servers, which could indicate exploitation attempts. 5. Educate Jenkins users about the risks of CSRF attacks and encourage cautious behavior when interacting with Jenkins interfaces, particularly avoiding clicking on suspicious links while authenticated. 6. Regularly update Jenkins core and plugins to the latest versions once patches addressing this vulnerability are available. 7. Implement multi-factor authentication (MFA) for Jenkins access to reduce the risk of credential misuse. 8. Use Jenkins credential masking and restrict credential scope to minimize the impact of any credential exposure. 9. Conduct security audits and penetration testing focusing on CI/CD pipelines to identify and remediate similar vulnerabilities proactively.
Description
A cross-site request forgery (CSRF) vulnerability in Jenkins CONS3RT Plugin 1.0.0 and earlier allows attackers to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.