CVE-2022-41245: Jenkins Worksoft Execution Manager Plugin · Cross-Site Request Forgery
Affects Jenkins Worksoft Execution Manager PluginSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins project Jenkins Worksoft Execution Manager Plugin | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2022-41245, European organizations should take the following specific actions: 1) Immediately update the Jenkins Worksoft Execution Manager Plugin to the latest version where the vulnerability is patched. If an update is not yet available, consider disabling or uninstalling the plugin temporarily to eliminate exposure. 2) Implement strict CSRF protection mechanisms in Jenkins, including enabling the built-in CSRF protection features and validating that all plugins comply with these protections. 3) Audit and restrict the use of credentials stored in Jenkins, ensuring that only necessary credentials are stored and that access is tightly controlled and logged. 4) Monitor Jenkins logs for unusual activity, such as unexpected connections to external URLs or unauthorized credential usage. 5) Educate Jenkins users about phishing and social engineering risks that could facilitate CSRF attacks, emphasizing the importance of not clicking on suspicious links while authenticated to Jenkins. 6) Employ network segmentation and firewall rules to limit Jenkins server connectivity to only trusted endpoints, reducing the risk of attacker-controlled URL interactions. 7) Regularly review and rotate credentials stored in Jenkins to minimize the impact of potential credential exposure.
Description
A cross-site request forgery (CSRF) vulnerability in Jenkins Worksoft Execution Manager Plugin 10.0.3.503 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.