← Vulnerability feed

Vulnerability record · CVE-2020-13340 · published 8 October 2020

CVE-2020-13340: GitLab stored XSS in CI job log

Gitlab · Gitlab

GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2 contain a stored cross-site scripting flaw in the CI job log. Because the injected script persists in the job log and is served to other users viewing it, the flaw can compromise accounts and sessions beyond the original submitter.

8.7 CVSS 3.1 High EPSS 69% · top 0.7% CWE-79 · Cross-site scripting
8.7CVSS 3.1 base score, v2 3.5
69%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
6References
17 Jun 2026Last modified by NVD

Description

An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2: Stored XSS in CI Job Log

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

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 19 September 2026. Confidence: medium.

high priorityHigh CVSS (8.7) with scope change and very high EPSS probability, though no KEV listing or documented exploitation.

What it is

GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2 contain a stored cross-site scripting flaw in the CI job log. Because the injected script persists in the job log and is served to other users viewing it, the flaw can compromise accounts and sessions beyond the original submitter.

Impact

An attacker can execute arbitrary script in the browser of any user who views the affected CI job log, potentially stealing session tokens or acting as that user. The CVSS scope change (S:C) indicates the impact can extend beyond the vulnerable component.

Attack surface

Reached over the network through the GitLab web interface by a user who can influence CI job log content; the vector requires low privileges (PR:L) and user interaction (UI:R) from the victim who views the log.

Exploitation

Not listed in CISA KEV and no public exploit or ransomware use is documented in the record, but EPSS is high at 0.686 (99.3rd percentile), suggesting elevated likelihood of exploitation activity.

What to do

  • Upgrade GitLab to 13.2.10, 13.3.7, 13.4.2 or later, which contain the fix.
  • Restrict who can create or modify CI jobs and job log output to trusted users.
  • Sanitize or escape untrusted content written into CI job logs.
  • Apply a Content Security Policy to reduce script execution impact in the GitLab UI.

Detection

  • Review CI job logs for embedded script tags or HTML event handlers.
  • Monitor GitLab access logs for anomalous requests to job log endpoints.
  • Alert on user reports of unexpected script execution or session anomalies after viewing job logs.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2020-13340 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

10.0CVE-2026-85706GitLab CE/EE repository commits API path traversal allows unauthenticated file readGitLab CE/EE contains improper path confinement and missing authentication enforcement in the repository commits API, allowing an unauthenticated use…KEVEPSS 91%analysed10.0CVE-2021-22205GitLab CE/EE image parser flaw allows unauthenticated remote code executionGitLab CE/EE failed to properly validate image files passed to a file parser, allowing code injection that leads to remote command execution. The fla…KEVEPSS 100%analysed9.8CVE-2023-7028GitLab CE/EE password reset sent to unverified email, enabling account takeoverGitLab CE/EE versions from 16.1 through 16.7 before their fixed releases could deliver account password reset emails to an unverified email address. …KEVEPSS 95%analysed9.8CVE-2021-22175GitLab unauthenticated SSRF via internal webhook requestsGitLab is vulnerable to server-side request forgery when requests to the internal network for webhooks are enabled. The flaw affects all versions sta…KEVEPSS 53%analysed7.5CVE-2021-39935GitLab CI Lint API server-side request forgeryGitLab CE/EE contains a server-side request forgery flaw in the CI Lint API affecting versions from 10.5 before 14.3.6, 14.4 before 14.4.4, and 14.5 …KEVEPSS 36%analysed10.0CVE-2020-13300Gitlab incorrect authorization vulnerabilityGitLab CE/EE version 13.3 prior to 13.3.4 was vulnerable to an OAuth authorization scope change without user consent in the middle of the authorizati…EPSS 1.3%10.0CVE-2019-9174Gitlab server-side request forgery (ssrf) vulnerabilityAn issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows SSRF.EPSS 2.0%10.0CVE-2018-18843Gitlab server-side request forgery (ssrf) vulnerabilityThe Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4.4 has SSRF.EPSS 1.6%

Source: NIST National Vulnerability Database (record CVE-2020-13340), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.