CVE Vulnerability Catalog

The Export All Posts, Products, Orders, Refunds & Users plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 2.19. Missing or incorrect nonce validation on the parseData function allows unauthenticated attackers to export sensitive information (user data, email addresses, password hashes, WooCommerce data) to an attacker-controlled file path via a forged request if they can trick an administrator into clicking a link.

In the Modem module, a possible system crash exists due to improper input validation. This could lead to remote denial of service if a UE connects to a rogue base station controlled by the attacker, with no additional execution privileges or user interaction needed.

In GPU pdma, there is a possible information disclosure due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed, but user interaction is required for exploitation.

In GPU pdma, there is a possible memory corruption due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed, but user interaction is required for exploitation.

In Modem, there is a possible application crash due to improper input validation. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation.

The BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks, WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'timestamp' attribute in all versions up to, and including, 2.2.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with Contributor-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

SmartTouchCall prior to version 1.0.1.1 has improper verification of the source of a communication channel, allowing remote attackers to access sensitive information. User interaction is required to trigger the vulnerability.

Improper input validation in Samsung Account prior to version 15.5.01.1 allows a local attacker to execute arbitrary script.

Improper input validation in Samsung Internet prior to version 29.0.0.48 allows local attackers to inject arbitrary script.

Incorrect default permissions in Samsung Cloud Assistant prior to version 8.0.03.8 allows a local attacker to access partial data in the sandbox.

Improper export of Android application components in Galaxy Store for Galaxy Watch before version 1.0.06.29 allows a local attacker to install arbitrary applications on Galaxy Store.

An out-of-bounds read exists in libimagecodec.quram.so prior to SMR Dec-2025 Release 1. A remote attacker can access out-of-bounds memory.

An out-of-bounds write exists in libimagecodec.quram.so prior to SMR Dec-2025 Release 1. A remote attacker can access out-of-bounds memory.

An out-of-bounds write exists in parsing IFD tag in libimagecodec.quram.so prior to SMR Dec-2025 Release 1. A remote attacker can access out-of-bounds memory.

Out-of-bounds read vulnerability in bootloader prior to SMR Dec-2025 Release 1 allows physical attackers to access out-of-bounds memory.

Improper input validation in libsec-ril.so prior to SMR Dec-2025 Release 1 allows local privileged attackers to write out-of-bounds memory.

Improper export of Android application components in Dynamic Lockscreen before SMR Dec-2025 Release 1 allows local attackers to access files with Dynamic Lockscreen's privilege.

Out-of-bounds write in decoding metadata in fingerprint trustlet prior to SMR Dec-2025 Release 1 allows local privileged attackers to write out-of-bounds memory.

Prior to version 12.5.0, the fastify-reply-from plugin allows an attacker to access routes that are not allowed by crafting a malicious URL, even though reply.from is defined for specific routes.

W Angularze, przed wersjami 21.0.2, 20.3.15 i 19.2.17, zidentyfikowano podatność typu Stored Cross-Site Scripting (XSS) w kompilatorze szablonów. Problem wynika z niekompletności wewnętrznego schematu zabezpieczeń kompilatora, co pozwala atakującym na obejście wbudowanej sanitizacji bezpieczeństwa Angulara.