CVE-2020-11445 Vulnerability Analysis & Exploit Details

CVE-2020-11445
Vulnerability Scoring

5.3
/10
Significant Risk

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

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-2020-11445 Details

Status: Analyzed

Last updated: 🕦 21 Jul 2021, 11:39 UTC
Originally published on: 🕓 01 Apr 2020, 04:15 UTC

Time between publication and last update: 476 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:L/I:N/A:N

CVE-2020-11445 Vulnerability Summary

CVE-2020-11445: TP-Link cloud cameras through 2020-02-09 allow remote attackers to bypass authentication and obtain sensitive information via vectors involving a Wi-Fi session with GPS enabled, aka CNVD-2020-04855.

Assessing the Risk of CVE-2020-11445

Access Complexity Graph

The exploitability of CVE-2020-11445 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-2020-11445

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

  • Confidentiality: Low
    CVE-2020-11445 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2020-11445 poses no threat to data integrity.
  • Availability: None
    CVE-2020-11445 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-2020-11445 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:tp-link:nc450_firmware:1.0.15:160920:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.0.15:160920:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.1.1:160928:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.1.1:160928:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.1.2:161013:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.1.2:161013:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.1.6:161124:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.1.6:161124:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.3.4:171130:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.3.4:171130:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.5.0:181022:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.5.0:181022:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.5.3:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.5.3:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.5.4:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.5.4:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.5.5:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.5.5:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:1.5.0_build_181022:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:1.5.0_build_181022:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc450_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc450_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc450:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc450:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.0.5:160804:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.0.5:160804:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.0.6:161114:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.0.6:161114:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.4.1:180720:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.4.1:180720:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.0:181123:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.0:181123:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.1:190805:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.1:190805:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.2:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.2:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.3:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.3:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.4:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.4:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:1.5.1_build_190805:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:1.5.1_build_190805:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc260_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc260_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc260:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc260:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.0.8:160108:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.0.8:160108:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.0.10:160321:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.0.10:160321:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.2.1:170515:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.2.1:170515:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.3.0:171205:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.3.0:171205:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.3.0:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.3.0:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:1.3.0_build171205:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:1.3.0_build171205:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc250_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc250_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc250:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc250:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.0.3:160108:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.0.3:160108:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.2.1:170515:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.2.1:170515:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.3.0:171205:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.3.0:171205:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.3.0:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.3.0:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:1.3.0_build_171205:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:1.3.0_build_171205:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc230_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc230_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc230:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc230:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.1.12:160321_a:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.1.12:160321_a:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.1.12:160321_b:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.1.12:160321_b:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.1.14:161219:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.1.14:161219:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.2.0:170516:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.2.0:170516:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.3.0:180105:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.3.0:180105:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.3.0:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.3.0:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:1.3.0_build_180105:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:1.3.0_build_180105:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc220_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc220_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc220:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.3:160229:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.3:160229:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.4:160412:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.4:160412:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.9:171214:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.9:171214:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.9:200304:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.9:200304:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.11:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.11:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:1.0.9_build_171214:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:1.0.9_build_171214:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc210_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc210_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc210:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc210:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.6:160108_a:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.6:160108_a:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.6:160108_b:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.6:160108_b:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.7:160315_a:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.7:160315_a:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.7:160315_b:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.7:160315_b:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.8:171109:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.8:171109:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.9:200225:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.9:200225:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.10:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.10:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.11:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.11:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2.1.8_build_171109:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2.1.8_build_171109:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:nc200_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:nc200_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:nc200:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:nc200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:kc300s2_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:kc300s2_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:kc300s2:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:kc300s2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:kc310s2_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:kc310s2_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:kc310s2:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:kc310s2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:kc200_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:kc200_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:kc200:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:kc200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c200_firmware:1.1.22:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c200_firmware:1.1.22:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c200_firmware:1.2.2:build_220725:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c200_firmware:1.2.2:build_220725:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.4:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.4:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.9:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.9:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c200_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c200_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:tapo_c200:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:tapo_c200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c100_firmware:1.1.15:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c100_firmware:1.1.15:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tapo_c100_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tapo_c100_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:tapo_c100:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:tapo_c100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tl-sc3430_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tl-sc3430_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:tl-sc3430:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:tl-sc3430:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tl-sc3430n_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tl-sc3430n_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:tl-sc3430n:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:tl-sc3430n:-:*:*:*:*:*:*:*
  • cpe:2.3:o:tp-link:tl-sc4171g_firmware:2020-02-09:*:*:*:*:*:*:*
    cpe:2.3:o:tp-link:tl-sc4171g_firmware:2020-02-09:*:*:*:*:*:*:*
  • cpe:2.3:h:tp-link:tl-sc4171g:-:*:*:*:*:*:*:*
    cpe:2.3:h:tp-link:tl-sc4171g:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-11445: 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-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
  • CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
  • CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
  • CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...
  • CVE-2025-3404 – The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the savePackage func...