CVE-2023-49804 Vulnerability Analysis & Exploit Details

CVE-2023-49804
Vulnerability Scoring

6.7
/10
High Risk

If left unpatched, CVE-2023-49804 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level 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-2023-49804 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:33 UTC
Originally published on: 🕚 11 Dec 2023, 23:15 UTC

Time between publication and last update: 345 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-49804 Vulnerability Summary

CVE-2023-49804: Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, when a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out. This behavior persists consistently, even after system restarts or browser restarts. This vulnerability allows unauthorized access to user accounts, compromising the security of sensitive information. The same vulnerability was partially fixed in CVE-2023-44400, but logging existing users out of their accounts was forgotten. To mitigate the risks associated with this vulnerability, the maintainers made the server emit a `refresh` event (clients handle this by reloading) and then disconnecting all clients except the one initiating the password change. It is recommended to update Uptime Kuma to version 1.23.9.

Assessing the Risk of CVE-2023-49804

Access Complexity Graph

The exploitability of CVE-2023-49804 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-2023-49804

The exploitability of CVE-2023-49804 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-2023-49804, 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-2023-49804, 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-2023-49804 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-49804 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-49804 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.042% (probability of exploit)

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

CVE-2023-49804 References

External References

CWE Common Weakness Enumeration

CWE-384

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Credential Falsification through Forging CAPEC-196 An attacker creates a false but functional session credential in order to gain or usurp access to a service. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. If an attacker is able to forge valid session credentials they may be able to bypass authentication or piggy-back off some other authenticated user's session. This attack differs from Reuse of Session IDs and Session Sidejacking attacks in that in the latter attacks an attacker uses a previous or existing credential without modification while, in a forging attack, the attacker must create their own credential, although it may be based on previously observed credentials.
  • 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.
  • Accessing/Intercepting/Modifying HTTP Cookies CAPEC-31 This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
  • Manipulating Opaque Client-based Data Tokens CAPEC-39 In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.
  • 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.
  • Session Fixation CAPEC-61 The attacker induces a client to establish a session with the target software using a session identifier provided by the attacker. Once the user successfully authenticates to the target software, the attacker uses the (now privileged) session identifier in their own transactions. This attack leverages the fact that the target software either relies on client-generated session identifiers or maintains the same session identifiers after privilege elevation.

Vulnerable Configurations

  • cpe:2.3:a:dockge.kuma:dockge:-:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:-:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:dockge.kuma:dockge:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:dockge.kuma:dockge:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.4:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.11.4:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.12.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.13.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.17.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.4:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.4:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.5:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.18.5:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.4:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.4:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.5:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.5:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.6:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.19.6:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.20.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.2:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.2:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.2:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.2:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.21.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.22.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.1:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.1:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.2:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.2:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.3:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.3:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.4:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.4:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.5:-:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.5:-:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.5:beta0:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.5:beta0:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.6:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.6:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.7:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.7:*:*:*:*:*:*:*
  • cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.8:*:*:*:*:*:*:*
    cpe:2.3:a:uptime.kuma:uptime_kuma:1.23.8:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-49804: 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-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...
  • CVE-2021-4455 – The Wordpress Plugin Smart Product Review plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all v...