VulDB Recent Entries

A vulnerability classified as problematic was found in YugabyteDB. This vulnerability affects unknown code of the component gflag Configuration Handler. The manipulation leads to insertion of sensitive information into sent data. This vulnerability was named CVE-2025-8862. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical has been found in GIMP on macOS. This affects an unknown part of the component TCC Handler. The manipulation leads to incorrect default permissions. This vulnerability is uniquely identified as CVE-2025-8672. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in 2100 Technology Official Document Management System 5.0.89.0/5.0.89.1/5.0.89.2. It has been rated as critical. Affected by this issue is some unknown functionality. The manipulation leads to authentication bypass by spoofing. This vulnerability is handled as CVE-2025-8853. The attack may be launched remotely. There is no exploit available.

A vulnerability was found in code-projects eBlog Site 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /native/admin/save-slider.php of the component File Upload Module. The manipulation leads to unrestricted upload. This vulnerability is known as CVE-2025-8859. The attack can be launched remotely. Furthermore, there is an exploit available.

A vulnerability was found in Broadcom Symantec PGP Encryption 11.0.1. It has been classified as problematic. Affected is an unknown function. The manipulation leads to cross site scripting. This vulnerability is traded as CVE-2025-8661. It is possible to launch the attack remotely. There is no exploit available.

A vulnerability was found in Broadcom Symantec PGP Encryption 11.0.1 and classified as problematic. This issue affects some unknown processing. The manipulation leads to privilege escalation. The identification of this vulnerability is CVE-2025-8660. The attack may be initiated remotely. There is no exploit available.

A vulnerability has been found in Google Keras up to 3.10.0 and classified as problematic. This vulnerability affects the function Model.load_model. The manipulation leads to deserialization. This vulnerability was named CVE-2025-8747. An attack has to be approached locally. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability, which was classified as problematic, was found in CBX Restaurant Booking Plugin up to 1.2.1 on WordPress. This affects an unknown part of the component Setting Handler. The manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2025-7965. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in OpenHarmony up to 5.0.3.x. Affected by this issue is some unknown functionality. The manipulation leads to memory leak. This vulnerability is handled as CVE-2025-27562. It is possible to launch the attack on the local host. There is no exploit available.

A vulnerability classified as problematic was found in OpenHarmony up to 5.0.3. Affected by this vulnerability is an unknown functionality. The manipulation leads to type confusion. This vulnerability is known as CVE-2025-27536. Attacking locally is a requirement. There is no exploit available.

A vulnerability classified as problematic has been found in OpenHarmony up to 5.0.3. Affected is an unknown function. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2025-26690. Local access is required to approach this attack. There is no exploit available.

A vulnerability was found in OpenHarmony up to 5.0.3. It has been rated as problematic. This issue affects some unknown processing. The manipulation leads to denial of service. The identification of this vulnerability is CVE-2025-25212. An attack has to be approached locally. There is no exploit available.

A vulnerability was found in OpenHarmony up to 5.0.3. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to memory leak. This vulnerability was named CVE-2025-24925. The attack needs to be approached locally. There is no exploit available.

A vulnerability was found in OpenHarmony up to 5.0.3. It has been classified as problematic. This affects an unknown part. The manipulation leads to memory leak. This vulnerability is uniquely identified as CVE-2025-24844. It is possible to launch the attack on the local host. There is no exploit available.

A vulnerability was found in OpenHarmony up to 5.0.3 and classified as critical. Affected by this issue is some unknown functionality of the component tcb. The manipulation leads to race condition. This vulnerability is handled as CVE-2025-27577. Attacking locally is a requirement. There is no exploit available.

A vulnerability has been found in OpenHarmony up to 5.0.3 and classified as critical. Affected by this vulnerability is an unknown functionality of the component tcb. The manipulation leads to use after free. This vulnerability is known as CVE-2025-27128. Local access is required to approach this attack. There is no exploit available.

A vulnerability, which was classified as critical, was found in OpenHarmony up to 5.0.3. Affected is an unknown function of the component tcb. The manipulation leads to race condition. This vulnerability is traded as CVE-2025-25278. An attack has to be approached locally. There is no exploit available.

A vulnerability, which was classified as critical, has been found in OpenHarmony up to 5.0.3. This issue affects some unknown processing of the component tcb. The manipulation leads to use after free. The identification of this vulnerability is CVE-2025-24298. The attack needs to be approached locally. There is no exploit available.

A vulnerability classified as critical was found in bulletphysics bullet3 up to 3.25. This vulnerability affects unknown code of the component LoadOFF. The manipulation leads to buffer overflow. This vulnerability was named CVE-2025-8854. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic has been found in WuKongOpenSource WukongCRM 11.0. This affects an unknown part of the file /adminFile/upload of the component API Response Handler. The manipulation leads to information exposure through error message. This vulnerability is uniquely identified as CVE-2025-8852. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.