CVE-2018-20752 Vulnerability Analysis & Exploit Details

CVE-2018-20752
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2018-20752 has severe implications, demanding immediate intervention.

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-2018-20752 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:02 UTC
Originally published on: 🕘 04 Feb 2019, 21:29 UTC

Time between publication and last update: 2116 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2018-20752 Vulnerability Summary

CVE-2018-20752: An issue was discovered in Recon-ng before 4.9.5. Lack of validation in the modules/reporting/csv.py file allows CSV injection. More specifically, when a Twitter user possesses an Excel macro for a username, it will not be properly sanitized when exported to a CSV file. This can result in remote code execution for the attacker.

Assessing the Risk of CVE-2018-20752

Access Complexity Graph

The exploitability of CVE-2018-20752 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-2018-20752

With low attack complexity and no required privileges, CVE-2018-20752 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-2018-20752, 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-2018-20752, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2018-20752 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2018-20752 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2018-20752 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.676% (probability of exploit)

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

CVE-2018-20752 References

External References

CWE Common Weakness Enumeration

CWE-1236

Vulnerable Configurations

  • cpe:2.3:a:recon-ng_project:recon-ng:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.5.7:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:3.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:3.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.9:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.10:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.10:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.11:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.11:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.12:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.12:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.1.13:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.1.13:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.7.5:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:recon-ng_project:recon-ng:4.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:recon-ng_project:recon-ng:4.9.4:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2018-20752: 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-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...
  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...