CVE-2013-5661 Vulnerability Analysis & Exploit Details

CVE-2013-5661
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2013-5661 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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-2013-5661 Details

Status: Modified

Last updated: 🕜 21 Nov 2024, 01:57 UTC
Originally published on: 🕖 05 Nov 2019, 19:15 UTC

Time between publication and last update: 1842 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2013-5661 Vulnerability Summary

CVE-2013-5661: Cache Poisoning issue exists in DNS Response Rate Limiting.

Assessing the Risk of CVE-2013-5661

Access Complexity Graph

The exploitability of CVE-2013-5661 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-2013-5661

CVE-2013-5661 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-2013-5661, 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-2013-5661, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2013-5661 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2013-5661 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2013-5661 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.113% (probability of exploit)

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

CVE-2013-5661 References

External References

CWE Common Weakness Enumeration

CWE-290

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Trusted Identifiers CAPEC-21 An adversary guesses, obtains, or "rides" a trusted identifier (e.g. session ID, resource ID, cookie, etc.) to perform authorized actions under the guise of an authenticated user or service.
  • Exploiting Trust in Client CAPEC-22 An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Creating a Rogue Certification Authority Certificate CAPEC-459 An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
  • Web Services API Signature Forgery Leveraging Hash Function Extension Weakness CAPEC-461 An adversary utilizes a hash function extension/padding weakness, to modify the parameters passed to the web service requesting authentication by generating their own call in order to generate a legitimate signature hash (as described in the notes), without knowledge of the secret token sometimes provided by the web service.
  • Signature Spoof CAPEC-473 An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.
  • Signature Spoofing by Misrepresentation CAPEC-476 An attacker exploits a weakness in the parsing or display code of the recipient software to generate a data blob containing a supposedly valid signature, but the signer's identity is falsely represented, which can lead to the attacker manipulating the recipient software or its victim user to perform compromising actions.
  • Session Credential Falsification through Prediction CAPEC-59 This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay) CAPEC-60 This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Bluetooth Impersonation AttackS (BIAS) CAPEC-667 An adversary disguises the MAC address of their Bluetooth enabled device to one for which there exists an active and trusted connection and authenticates successfully. The adversary can then perform malicious actions on the target Bluetooth device depending on the target’s capabilities.
  • Adversary in the Middle (AiTM) CAPEC-94 An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.

Vulnerable Configurations

  • cpe:2.3:a:isc:bind:9.8.0:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:a1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:a1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:b1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:b1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:p2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:p2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:p3:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:p3:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:p4:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:p4:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.0:alpha1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.0:alpha1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:b1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:b1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:b2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:b2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:b3:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:b3:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:beta2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:beta2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.1:beta3:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.1:beta3:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:b1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:b1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:rc2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:rc2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.2:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.2:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:p2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:p2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:p3:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:p3:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.3:p4:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.3:p4:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:p2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:p2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.4:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.4:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:b1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:b1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:b2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:b2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:p2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:p2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:rc2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:rc2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.5:beta2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.5:beta2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:b1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:b1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:p2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:p2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:rc2:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:rc2:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.6:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.6:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:-:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:-:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:p1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:p1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:w1:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:w1:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:rc1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:rc1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:rc2:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:rc2:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.7:beta1:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.7:beta1:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:-:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:-:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:rc1:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:rc1:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:rc2:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:rc2:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:beta1:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:beta1:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.8:beta2:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.8:beta2:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.8.9:p2:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.8.9:p2:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:isc:bind:9.9.0:-:*:*:*:*:*:*
    cpe:2.3:a:isc:bind:9.9.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:nsd:3.2.15:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:nsd:3.2.15:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:-:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:-:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.0.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.0.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.0.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.0.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.0.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.0.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:nic:knot_resolver:1.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:nic:knot_resolver:1.2.6:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2013-5661: 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 ...