Vuldb Updates

A vulnerability, which was classified as problematic, was found in Apache Tomcat up to 9.0.106. This affects an unknown function of the component APR Native Connector. The manipulation results in race condition. This vulnerability was named CVE-2025-52434. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.

A vulnerability identified as problematic has been detected in resolv up to 0.2.2/0.3.0/0.6.1 on Ruby. This issue affects some unknown processing. The manipulation leads to resource consumption. This vulnerability is traded as CVE-2025-24294. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability was found in AMD EPYC 9005 Processors, Ryzen AI 300 Processors, Ryzen 9000 Desktop Processors, Ryzen 9000HX Processors, Ryzen Al Max+, Ryzen Threadripper 9000 and EPYC Embedded 9000 Processors and classified as problematic. This affects an unknown function. Such manipulation leads to incomplete cleanup. This vulnerability is uniquely identified as CVE-2025-0032. Local access is required to approach this attack. No exploit exists. It is suggested to upgrade the affected component.

A vulnerability classified as problematic has been found in AMD Ryzen 8000 Desktop Processors, Ryzen 7040 Mobile Processors with Radeon Graphics, Ryzen 6000 Processor with Radeon Graphics, Ryzen 7035 Processor with Radeon Graphics, Ryzen 7020 Processors with Radeon Graphics, Ryzen 7000 Mobile Processors, Ryzen Z1 Processors, Ryzen Embedded 7000 Processors, Ryzen Embedded V2000 Processors, Ryzen Embedded 8000 Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon PRO W6000 Graphics Products, Radeon RX 7000 Graphics Products, Radeon PRO W7000 Graphics Products, Radeon PRO V520 Graphics Products, Radeon PRO V620 Graphics Products and Radeon PRO V710 Graphics Products. This vulnerability affects unknown code of the component Crash Defender. Performing manipulation results in improper removal of sensitive information before storage or transfer. This vulnerability is reported as CVE-2025-0011. The attack requires a local approach. No exploit exists.

A vulnerability was found in TianoCore EDK2 up to stable202505. It has been declared as critical. Affected by this issue is some unknown functionality of the component BIOS. The manipulation results in protection mechanism failure. This vulnerability is reported as CVE-2025-3770. The attack requires a local approach. No exploit exists.

A vulnerability has been found in AMD Ryzen Threadripper 3000 Processors, Ryzen Threadripper PRO 5000 WX-Series Processors, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen Threadripper PRO 3000 WX-Series Processors, Ryzen 3000 Mobile Processors with Radeon Graphics, Ryzen 8040 Mobile Processors with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 8000 Desktop Processors, Ryzen 7040 Mobile Processors with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 6000 Processors with Radeon Graphics, Ryzen 7045 Mobile Processors with Radeon Graphics, Ryzen 7035 Processors with Radeon Graphics, Ryzen 7000 Desktop Processors, Ryzen 7030 Mobile Processors with Radeon Graphics, Ryzen 9000 Desktop Processors, Ryzen 3000 Desktop Processors, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen 4000 Desktop Processors, Ryzen 5000 Desktop Processors, EPYC Embedded 3000 Processors, EPYC Embedded 7002 Processors, EPYC Embedded 7003 Processors, EPYC Embedded 9004 Processors, Ryzen Embedded 5000 Processors, Ryzen Embedded V2000 Processors, Ryzen Embedded V3000 Processors, EPYC Embedded 97X4 Processors, Ryzen Embedded 7000 Processors, EPYC 9004 Processors, EPYC 7003 Processors, EPYC 7002 Processors, EPYC 7001 Processors, EPYC 4004 Processors and EPYC 8004 Processors and classified as critical. The impacted element is an unknown function of the component SPD. This manipulation causes improper input validation. This vulnerability is handled as CVE-2024-36354. It is possible to launch the attack on the local host. There is not any exploit available. The affected component should be upgraded.

A vulnerability was found in AMD Ryzen 7035 Processor with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 7000 Desktop Processors, Ryzen 8040 Mobile Processors with Radeon Graphics, Ryzen 4000 Desktop Processor with Radeon Graphics, Ryzen 6000 Processor with Radeon Graphics, Ryzen 7020 Processors with Radeon Graphics, Ryzen 7000 Mobile Processors, Ryzen 5000 Processors with Radeon Graphics, Ryzen 7000 Processors with Radeon Graphics, Ryzen 7040 Processors with Radeon Graphics, Ryzen 8000 Processor with Radeon Graphics, Ryzen 9000 Desktop Processors, Ryzen 4000 Desktop Processors, Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen 3000 Mobile Processors with Radeon Graphics, Ryzen Embedded 7000 Processors, Ryzen Embedded 8000 Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon PRO W6000 Graphics Products, Radeon RX 7000 Graphics Products, Radeon PRO W7000 Graphics Products, Radeon PRO V520 Graphics Products, Radeon PRO V620 Graphics Products and Radeon PRO V710 Graphics Products. It has been declared as problematic. Affected is an unknown function. Executing manipulation can lead to null pointer dereference. The identification of this vulnerability is CVE-2025-0009. The attack can only be executed locally. There is no exploit available.

A vulnerability has been found in Emplibot Plugin up to 1.0.9 on WordPress and classified as critical. Affected is the function emplibot_call_webhook_with_error. The manipulation leads to server-side request forgery. This vulnerability is traded as CVE-2025-11970. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability was found in Colibri Page Builder Plugin up to 1.0.335 on WordPress and classified as problematic. Affected by this vulnerability is the function colibri_loop. The manipulation results in cross site scripting. This vulnerability is known as CVE-2025-11376. It is possible to launch the attack remotely. No exploit is available.

A vulnerability classified as problematic has been found in Social Media Auto Publish Plugin up to 3.6.5 on WordPress. This impacts an unknown function. Performing manipulation of the argument PostMessage results in cross site scripting. This vulnerability is cataloged as CVE-2025-12076. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability was found in Brizy Plugin up to 2.7.16 on WordPress. It has been classified as problematic. The impacted element is the function get_users. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2025-0969. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability, which was classified as critical, has been found in URL Shortener Plugin Plugin up to 3.0.7 on WordPress. This affects an unknown function. Performing manipulation of the argument analytic_id results in sql injection. This vulnerability is reported as CVE-2025-10738. The attack is possible to be carried out remotely. No exploit exists.

A vulnerability classified as problematic was found in myCred Plugin up to 2.9.7 on WordPress. The impacted element is the function cashcred_pay_now. Such manipulation leads to missing authorization. This vulnerability is documented as CVE-2025-12362. The attack can be executed remotely. There is not any exploit available.

A vulnerability has been found in Export WP Page to Static HTML & PDF Plugin up to 4.3.4 on WordPress and classified as problematic. The impacted element is an unknown function of the component Log File Handler. Performing manipulation results in sensitive information in log files. This vulnerability is known as CVE-2025-11693. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability classified as problematic was found in Header Footer Script Adder Plugin up to 2.0.5 on WordPress. Affected is an unknown function. Executing manipulation can lead to cross site scripting. This vulnerability is registered as CVE-2025-12109. It is possible to launch the attack remotely. No exploit is available.

A vulnerability was found in WP to LinkedIn Auto Publish Plugin up to 1.9.8 on WordPress. It has been rated as problematic. This vulnerability affects unknown code. Performing manipulation results in cross site scripting. This vulnerability was named CVE-2025-12077. The attack may be initiated remotely. There is no available exploit.

A vulnerability was found in Filter & Grids Plugin up to 3.2.0 on WordPress. It has been declared as critical. This affects an unknown part. Such manipulation of the argument phrase leads to sql injection. This vulnerability is uniquely identified as CVE-2025-10289. The attack can be launched remotely. No exploit exists.

A vulnerability marked as critical has been reported in Login Lockdown & Protection Plugin up to 2.14 on WordPress. Affected by this issue is some unknown functionality. Performing manipulation of the argument unblock_key results in improper access controls. This vulnerability is cataloged as CVE-2025-11707. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in Mavix Education Theme Plugin up to 1.0 on WordPress. Impacted is the function mavix_education_activate_plugin of the component Plugin Activation Handler. This manipulation causes missing authorization. This vulnerability appears as CVE-2025-11164. The attack may be initiated remotely. There is no available exploit.

A vulnerability labeled as critical has been found in Apple macOS, tvOS, visionOS, watchOS, iOS and iPadOS up to 26.0. This issue affects some unknown processing. The manipulation results in memory corruption. This vulnerability was named CVE-2025-43520. The attack needs to be approached locally. There is no available exploit. The affected component should be upgraded.