LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41239: Jenkins DotCi Plugin 2.40.00 and earlier does not escape the GitHub user name parameter provided to commit...

Jenkins DotCi Plugin 2.40.00 and earlier does not escape the GitHub user name parameter provided to commit notifications when displaying them in a build cause, resulting in a stored cross-site scripting (XSS) vulnerability.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Jenkins DotCi Plugin can store and later display unsafe GitHub user-name content in build-cause information. If an exposed Jenkins instance uses DotCi Plugin 2.40.00 or earlier, a user viewing affected build details could have script run in their browser.

Executive priority

Treat as a moderate application-security issue. It is not shown as actively exploited, but Jenkins is operationally sensitive, and stored XSS can affect trusted users who manage builds and delivery workflows.

Technical view

CVE-2022-41239 is a stored XSS issue in Jenkins DotCi Plugin 2.40.00 and earlier. The plugin fails to escape the GitHub user name parameter in commit notifications when rendering build causes. The CVSS vector indicates network reachability, low privileges, required user interaction, changed scope, and limited confidentiality and integrity impact.

Likely exposure

Exposure is limited to Jenkins environments with DotCi Plugin 2.40.00 or earlier installed. Risk is higher where commit notifications include GitHub identity data and Jenkins users routinely view build cause details.

Exploitation context

The bundle provides no evidence of CISA KEV listing or active exploitation. Exploitation requires a stored malicious value and a user viewing the affected Jenkins build-cause display, based on the CVSS user-interaction requirement.

Researcher notes

Key uncertainty is remediation status: the supplied bundle names affected versions but does not name a fixed release or mitigation. Analysis should stay tied to Jenkins advisory SECURITY-2884 and avoid claiming exploit activity without additional cited evidence.

Mitigation direction

  • Inventory Jenkins controllers for DotCi Plugin installations and versions.
  • Review Jenkins advisory SECURITY-2884 for current vendor remediation guidance.
  • Do not assume a fixed version from this bundle; verify with Jenkins sources.
  • Prioritize remediation for Jenkins instances accessed by many developers or administrators.

Validation and detection

  • Confirm whether DotCi Plugin is installed on each Jenkins controller.
  • Record the installed plugin version and flag 2.40.00 or earlier.
  • Review vulnerable build-cause display paths for exposure to commit notification data.
  • Check vulnerability tracking for remediation evidence tied to Jenkins advisory SECURITY-2884.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41239 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-41239Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jenkins projectJenkins DotCi Pluginunspecified, next of 2.40.00Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.