| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The PocketTouch and TouchPoint POS protocol includes a `SAVECONFIG` command that appears capable of overwriting till configuration files remotely.
An attacker with network access to the POS socket service may be able to submit a crafted `SAVECONFIG` command and replace or modify terminal configuration data. |
| ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value. |
| ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception.
An attacker able to observe network traffic between a PocketTouch device and a TouchPoint POS terminal can recover the socket password from captured packets. |
| ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers, and other intermediary records. |
| ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts. The interface also returns distinguishable responses for multiple authentication states, including different behavior when a `siteID` value is supplied. |
| The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF. An attacker-controlled website can cause an authenticated customer’s browser to submit a wallet top-up request and add an attacker-selected charge to the customer’s active cart. |
| ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for state-changing web requests. The affected functionality does not require a per-session CSRF token or otherwise verify that requests originated from an authorized application context.
An attacker who convinces an authenticated user to visit a malicious website may cause the user’s browser to submit unauthorized requests to the platform using the user’s active session. |
| NVIDIA Transformer Engine for Linux contains a vulnerability where a user could cause deserialization by loading untrusted data. A successful exploit of this vulnerability might lead to code execution, information disclosure, and denial of service. |
| NVIDIA Model Optimizer for Linux and Windows contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure. |
| Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in PocketBook / Obreey Products PocketBook Reader (Android) allows Exposure of Sensitive Information to an Unauthorized Actor.
This issue affects PocketBook Reader (Android): 5.65.0.39561.release (com.obreey.reader). |
| The firmware and flash memory store critical cryptographic secrets, such as global AES keys and network master keys, in unencrypted formats. Additionally, active session tokens (Store Pairing Tokens) are written to the flash in plaintext, exposing live network credentials. |
| Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in PocketBook / Obreey Products PocketBook Reader (Android) allows Exposure of Sensitive Information to an Unauthorized Actor.
This issue affects PocketBook Reader (Android): 5.65.0.39561.release (com.obreey.reader). |
| Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests. |
| matrix-hookshot is a Matrix bot for connecting to external services like GitHub, GitLab, JIRA, and more. Prior to 7.3.3, Hookshot can crash in src/Bridge.ts while processing a modern Matrix reply whose m.relates_to.m.in_reply_to.event_id identifies an event that the bot cannot read. Bridge event handling calls botClient.getEvent() for the parent event without catching the resulting M_NOT_FOUND error, allowing the rejected request to escape reply processing and terminate the service. This issue is fixed in version 7.3.3. |
| Filament Curator is a media picker plugin for Filament panels. From 3.0.0 until 3.7.9, 4.1.2, and 5.1.2, the Curator media panel accepts image/svg+xml files by default and stores and serves their markup inline without sanitization. An authenticated user with media-upload permission can store an SVG containing scripts, event-handler attributes, or javascript: URIs. When another panel user selects the View action, the SVG opens as a top-level browser document and its active content executes in the Filament application's origin. The script can perform authenticated same-origin actions as the viewing user and read same-origin data and script-accessible tokens. Panel thumbnails are not affected because they render through an image element that does not execute SVG script. This issue is fixed in versions 3.7.9, 4.1.2, and 5.1.2. |
| tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. From 2.1.0 until 2.2.5 for tiny-secp256k1 and from 2.2.2 until 2.2.5 for @bitcoin-js/tiny-secp256k1-asmjs, the three-argument xOnlyPointAddTweakCheck path ignores the backend failure return from xOnlyPointAddTweak when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer then still contains the original point, so a caller-controlled resultToCheck equal to that point can make the stale-buffer comparison return true even though no tweaked key exists. Protocols that rely on this helper to validate caller-controlled internal keys, tweaks, and comparison values can accept an invalid derived key. This issue is fixed in version 2.2.5. |
| Kiwi TCMS is an open source test management system. From 16.1 until 16.2, the account confirmation page’s incomplete validation of the next parameter accepts protocol-relative URLs because the version 16.1 fix for CVE-2026-54724 only requires the value to start with a slash. An unauthenticated attacker can craft a confirmation URL on a trusted Kiwi TCMS hostname that redirects a user to an external site, enabling phishing and related downstream confidentiality or integrity impacts when the user follows the link. This issue is fixed in version 16.2. |
| WPS Limit Login (wps-limit-login) before 1.5.9.5 contains an improper access control vulnerability that allows unauthenticated attackers to bypass login lockout protections by keying the per-attempt login counter and lockout map on the raw, non-canonicalized IPv6 client address. Attackers controlling a routable IPv6 /64 prefix can send each login attempt from a fresh address within that range, preventing any counter from reaching the lockout threshold and enabling effectively unlimited brute-force password guessing against WordPress accounts. |
| tac_plus-ng before commit d8493e0 contains a stack-based buffer overflow vulnerability that allows clients holding the TACACS+ shared key to overflow a stack buffer due to an operator precedence error in author_pak_looks_bogus() and accounting_pak_looks_bogus(). Attackers can send packets whose argument-length table exceeds the payload, causing eval_args() to read past the packet and memcpy() oversized cmd values into cmdline, crashing the daemon or executing code. |
| Pytition before 2.10 contains an insecure direct object reference vulnerability in the show_signatures view that allows registered users to delete other petitions' signatures by supplying foreign signature IDs. Attackers can post sequential signature IDs to their own petition's signatures page to permanently delete signatures from any user-owned petition and trigger confirmation emails to other signers. |