dbcve.org
Worksoft Execution ManagerApplication · Jenkins

CVE-2022-41245

HIGH · 8.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 10.0.3.503 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a CSRF vulnerability in the Jenkins Worksoft Execution Manager Plugin (version 10.0.3.503 and earlier) that allows authenticated attackers to craft malicious requests causing Jenkins to connect to attacker-controlled URLs using attacker-specified credentials IDs. The attack enables exfiltration of stored Jenkins credentials by tricking an authenticated user into executing the forged request.

MitigationUpdate the Worksoft Execution Manager Plugin to a patched version if available; otherwise, disable or remove the plugin. Additionally, ensure Jenkins global CSRF protection is enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Worksoft Execution ManagerApplication
Affected:<= 10.0.3.503

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Worksoft Execution Manager plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-cli.jar groovy = manager.pluginManager.plugins.each { if (it.shortName == 'worksoft-execution-manager') println "Found: ${it.displayName} version ${it.version}" }
    Affected if The plugin appears in the list of installed plugins. If not found, the vulnerability does not apply.
  2. Confirm the installed plugin version
    Locate the Worksoft Execution Manager plugin in the installed plugins list and note the version number shown. Compare it to the affected range: any version 10.0.3.503 or earlier.
    Affected if The version listed is 10.0.3.503 or lower (for example, 10.0.3.500, 10.0.3.4, 1.0.0, etc.). Versions higher than 10.0.3.503 are not affected.
  3. Check if the plugin is enabled
    In Manage Jenkins > Manage Plugins > Installed, verify the Worksoft Execution Manager plugin status is 'Enabled' or 'Active'. Alternatively, check the plugin configuration file in JENKINS_HOME/plugins/worksoft-execution-manager.jpi or .hpi.
    Affected if The plugin is installed and enabled. If the plugin is installed but disabled or not configured, the attack surface is reduced.
  4. Identify stored Jenkins credentials
    Navigate to Manage Jenkins > Manage Credentials. Review all credentials stored globally or within any domain, noting the credential IDs and types (username/password, SSH keys, secrets, etc.).
    Affected if Any credentials exist in Jenkins. The vulnerability allows an attacker to trigger Jenkins to connect to attacker-controlled URLs using attacker-specified credential IDs, potentially exfiltrating stored credential data.

Your environment is affected if the Worksoft Execution Manager plugin is installed with version 10.0.3.503 or earlier and contains stored credentials that could be exfiltrated through the CSRF flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 10.0.3.503
Interim mitigation

Update the Worksoft Execution Manager Plugin to a patched version if available; otherwise, disable or remove the plugin. Additionally, ensure Jenkins global CSRF protection is enabled.

Fix this in Worksoft Execution Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data