CVE-2026-105096 is a medium severity vulnerability in Omega Solution CoinEx Crypto 2025 affecting the Customer Profile API. Manipulating the argument ID in the /customer/ component can lead to authorization bypass. The vulnerability can be exploited remotely and has been publicly disclosed. The product appears to be retired or replaced, and the vendor has not responded to the disclosure. No patch or remediation information is available.
CVE-2026-105097 is a medium severity vulnerability in Omega Solution CoinEx Crypto 2025 affecting the Customer Information API component. The flaw involves manipulation of the argument ID in the /customer-currency/ file, leading to authorization bypass. Remote exploitation is possible, and exploit code is publicly available. The product website is no longer active, and the vendor has not responded to disclosure attempts. No patch or remediation information is available.
CVE-2026-105099 is a cross-site scripting (XSS) vulnerability in the Omega Solution CoinEx Crypto 2025 product. The flaw exists in an unknown functionality of the /user/ticket file within the Ticket Attachment Upload component. The vulnerability can be exploited remotely and requires low attack complexity with partial user interaction. The product website is no longer available, and the vendor did not respond to disclosure attempts. No patch or remediation information is available.
CVE-2026-105098 is an information disclosure vulnerability in Omega Solution CoinEx Crypto 2025. It affects an unknown function within the Support Ticket API component, specifically the /ticket/customer file. The flaw arises from manipulation of the status, page, or count arguments, allowing remote attackers to disclose information. The product appears to be retired or replaced, and the vendor has not responded to disclosure attempts. No patch or remediation is currently available.
ezBookkeeping versions 1.2.0 up to but not including 2.0.1 contain a privilege escalation vulnerability. Attackers with an API token can exploit the token refresh endpoint to obtain a full session token without proper authorization checks. This allows bypassing API token expiry and allowlists, potentially extending access privileges for 30 days.
LaraDashboard versions prior to 1.4.8 have an open redirect vulnerability in the EmailTemplateController's builder and builderEdit functions. This flaw allows remote attackers to craft URLs with an unvalidated redirect_url parameter that, when used by logged-in users with email template permissions, can redirect them to attacker-controlled phishing sites.
LaraDashboard versions before 1.4.8 have an incorrect authorization vulnerability that allows authenticated users with only the settings.view permission to access sensitive stored secrets. These secrets include plaintext AI provider API keys, mail credentials, passwords, and tokens accessible via the settings API endpoints. This vulnerability has a CVSS score of 6.5, indicating a high severity impact on confidentiality without affecting integrity or availability.
LaraDashboard versions before 1.4.8 perform advanced email validation on unauthenticated forgot-password and reset-password requests. This validation triggers DNS lookups and paid AbstractAPI verification calls. An unauthenticated attacker can abuse this by submitting arbitrary email addresses, exhausting the verification quota. Once exhausted, validation fails open for all public forms, potentially allowing invalid emails to pass unchecked. This behavior also allows attackers to probe domain resolution via DNS lookups.
LaraDashboard versions from 1.4.0 up to but not including 1.4.8 have a race condition vulnerability in the RegisterController::register function. This flaw allows unauthenticated attackers to bypass the per-IP daily registration limit by sending many concurrent registration requests, enabling bulk account creation and defeating anti-automation controls. The vulnerability has a CVSS score of 3.7, indicating medium severity.
LaraDashboard versions before 1.4.8 have an improper privilege management vulnerability that enables authenticated Admin users to escalate their privileges to Superadmin. This escalation is possible by editing or renaming roles, allowing attackers with the role.edit permission to rename their role to Superadmin or grant themselves user.login_as permissions. This access can lead to account takeover and the ability to perform core upgrade and module installation functions, potentially enabling code execution.
LaraDashboard versions prior to 1.4.8 have a path traversal vulnerability that allows unauthenticated attackers to read JSON files by manipulating the {lang} route segment. On Windows systems, attackers can use URL-encoded backslash sequences to escape the intended directory and access sensitive JSON files such as composer.json. The vulnerability has a CVSS score of 3.7, indicating a medium severity level.
The PyPI package 'caoxiltts' versions 0.1.0 and 0.1.1 contains malicious code that deploys a cryptocurrency miner instead of performing its advertised functions. This behavior is part of a campaign identified as 2026-10-voxeval, which involves malicious intent such as cryptomining. There is no CVSS score available for this threat.
An authorization bypass vulnerability exists in Ultimate Member up to version 2.13.1, allowing privilege escalation via a user-controlled key. This flaw enables attackers with limited privileges to escalate their access rights. The vulnerability is tracked as CVE-2026-96451 and has a high severity rating with a CVSS score of 8.8.
An incorrect authorization vulnerability in the FileSystem component of Google Chrome on Windows versions prior to 154.0.8037.97 allows a remote attacker to potentially execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page. This vulnerability has a high severity rating and requires user interaction for exploitation.
A use-after-free vulnerability exists in the Contextual Tasks component of Google Chrome on Windows versions prior to 154.0.8037.97. This flaw allows a remote attacker who has compromised the renderer process to potentially execute arbitrary code outside the sandbox by crafting a malicious HTML page. The vulnerability has a high severity rating.
An integer overflow vulnerability exists in the Skia component of Google Chrome versions prior to 154.0.8037.97. This flaw allows a remote attacker to leak cross-origin data by crafting a malicious HTML page. The vulnerability has a medium severity rating with a CVSS score of 4.3 and does not affect data integrity or availability. No known exploits have been reported in the wild. Affected versions include all versions before 154.0.8037.97 and specifically version 146.20260311+dfsg-4ubuntu1.
yaml-cpp version 0.9.0 and several other specified versions contain a vulnerability in the src/scanner.cpp component, specifically in the Scanner::PopIndent() and Scanner::PushIndentTo() functions. This flaw allows a remote attacker to obtain sensitive information. The issue has a medium severity rating with a CVSS score of 5.1. No patch or remediation details are currently available.
A path traversal vulnerability exists in pnpm versions prior to 10.34.5 and from 11.0.0 up to but not including 11.11.0. This flaw allows attacker-controlled package names in the pnpm-lock.yaml file to write files outside the intended node_modules directory during installation. Exploitation can lead to arbitrary code execution if lifecycle scripts are enabled. The vulnerability is fixed in versions 10.34.5 and 11.11.0.
A vulnerability in pnpm before versions 10.34.5 and 11.11.0 allows a tarball dependency's manifest name to escape the node_modules directory via path traversal during installation. This can lead to arbitrary file write or overwrite on the filesystem, potentially replacing critical files such as shell startup scripts, Git hooks, or installed package code, which may result in code execution. The issue is due to improper rejection of slash characters in scoped package names. The vulnerability is fixed in pnpm versions 10.34.5 and 11.11.0.