Worksoft Execution ManagerApplication · Jenkins
CVE-2022-41246
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 · uneditedA missing permission check in Jenkins Worksoft Execution Manager Plugin 10.0.3.503 and earlier allows attackers with Overall/Read permission 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 · moderate confidenceThe Worksoft Execution Manager Plugin lacks a permission check before allowing use of stored credentials, allowing any user with Overall/Read permission to leverage attacker-specified credential IDs to connect to attacker-controlled URLs and capture stored credentials.
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
<= 10.0.3.503CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Worksoft Execution Manager Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins for worksoft* files)Affected if The Worksoft Execution Manager Plugin appears in the installed plugins list
-
Check installed plugin versionIn Manage Plugins > Installed, find Worksoft Execution Manager and note the version column, or inspect $JENKINS_HOME/plugins/worksoftExecutionManager/META-INF/MANIFEST.MF for the Plugin-VersionAffected if Version is 10.0.3.503 or lower
-
Confirm plugin is actively configuredNavigate to Manage Jenkins > Configure System and look for 'Worksoft Execution Manager' configuration section, or check $JENKINS_HOME/config.xml for worksoft-related configuration entriesAffected if Worksoft Execution Manager configuration section exists and contains endpoint or credential settings
-
Check for stored credentials accessible to low-privilege usersReview credentials stored in Jenkins: go to Credentials > System > Global credentials, or query $JENKINS_HOME/credentials.xml for any Worksoft-related credentials (domain, username, password fields)Affected if Any credentials are stored in Jenkins that the Worksoft plugin could access
-
Verify user permission levelsNavigate to Manage Jenkins > Manage Users and check which users have Overall/Read permission (default for any authenticated user), or review $JENKINS_HOME/users/ directoryAffected if There are users or groups with Overall/Read permission (which is the minimum required to exploit this vulnerability)
If the Worksoft Execution Manager Plugin version is 10.0.3.503 or lower AND the plugin is installed with any stored credentials, any user with Overall/Read permission can exploit this vulnerability to capture credentials via attacker-controlled URLs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Worksoft Execution Manager Plugin to a version that implements proper permission checks before credential usage, and review stored credentials for potential compromise.
Fix this in Worksoft Execution Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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