CVE-2019-6781 Vulnerability Analysis & Exploit Details

CVE-2019-6781
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-6781 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2019-6781 Details

Status: Analyzed

Last updated: 🕟 20 Mar 2025, 16:52 UTC
Originally published on: 🕓 17 May 2019, 16:29 UTC

Time between publication and last update: 2134 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-6781 Vulnerability Summary

CVE-2019-6781: An Improper Input Validation issue was discovered in GitLab Community and Enterprise Edition before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It was possible to use the profile name to inject a potentially malicious link into notification emails.

Assessing the Risk of CVE-2019-6781

Access Complexity Graph

The exploitability of CVE-2019-6781 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-6781

With low attack complexity and no required privileges, CVE-2019-6781 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-6781, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-6781, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2019-6781 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2019-6781 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2019-6781 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.085% (probability of exploit)

EPSS Percentile: 38.77% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 61.23% of others.

CVE-2019-6781 References

External References

CWE Common Weakness Enumeration

CWE-601

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross-Site Flashing CAPEC-178 An attacker is able to trick the victim into executing a Flash document that passes commands or calls to a Flash player browser plugin, allowing the attacker to exploit native Flash functionality in the client browser. This attack pattern occurs where an attacker can provide a crafted link to a Flash document (SWF file) which, when followed, will cause additional malicious instructions to be executed. The attacker does not need to serve or control the Flash document. The attack takes advantage of the fact that Flash files can reference external URLs. If variables that serve as URLs that the Flash application references can be controlled through parameters, then by creating a link that includes values for those parameters, an attacker can cause arbitrary content to be referenced and possibly executed by the targeted Flash application.

Vulnerable Configurations

  • cpe:2.3:a:gitlab:gitlab:11.5.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:-:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:-:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:-:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:-:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc1:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc1:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc1:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc1:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc10:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc10:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc10:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc10:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc11:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc11:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc11:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc11:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc12:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc12:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc12:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc12:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc13:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc13:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc13:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc13:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc2:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc2:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc2:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc2:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc3:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc3:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc3:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc3:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc4:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc4:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc4:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc4:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc5:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc5:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc5:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc5:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc6:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc6:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc6:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc6:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc7:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc7:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc7:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc7:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc8:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc8:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc8:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc8:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc9:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc9:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.0:rc9:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.0:rc9:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.8:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.8:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.9:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.9:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.5.9:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.5.9:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.6.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.6.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:11.7.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:11.7.2:*:*:*:enterprise:*:*:*

Protect Your Infrastructure against CVE-2019-6781: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3797 – A vulnerability classified as critical was found in SeaCMS up to 13.3. This vulnerability affects unknown code of the file /admin_topic.php?action=...
  • CVE-2025-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...