Vuldb Updates

A vulnerability identified as critical has been detected in eosphoros-ai db-gpt 0.7.0. The impacted element is the function agent.hub.controller.refresh_plugins of the file /v1/personal/agent/upload of the component ZIP File Handler. The manipulation leads to unrestricted upload. This vulnerability is documented as CVE-2025-51459. The attack can be initiated remotely. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

A vulnerability classified as critical was found in cvat-ai cvat up to 2.41.x. This affects an unknown function. Executing manipulation can lead to improper authentication. The identification of this vulnerability is CVE-2025-54573. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.

A vulnerability described as problematic has been identified in yangzongzhuan RuoYi up to 4.8.1. The affected element is the function Edit of the file /system/notice/edit. The manipulation of the argument noticeTitle/noticeContent results in cross site scripting. This vulnerability is known as CVE-2025-8847. It is possible to launch the attack remotely. Furthermore, an exploit is available.

A vulnerability categorized as problematic has been discovered in freescout-help-desk freescout up to 1.8.185. This issue affects the function Helper::decrypt. Executing manipulation can lead to deserialization. The identification of this vulnerability is CVE-2025-54366. The attack may be launched remotely. There is no exploit available. It is advisable to upgrade the affected component.

A vulnerability described as critical has been identified in RooCodeInc Roo-Code up to 3.23.18. Impacted is an unknown function. Executing manipulation can lead to command injection. This vulnerability is handled as CVE-2025-54377. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.

A vulnerability classified as problematic was found in yangzongzhuan RuoYi up to 4.8.1. The impacted element is an unknown function of the component Image Source Handler. The manipulation results in improper restriction of rendered ui layers. This vulnerability is identified as CVE-2025-7903. The attack can be executed remotely. Additionally, an exploit exists.

A vulnerability, which was classified as problematic, has been found in Google Go up to 1.23.10/1.24.4. This affects an unknown part of the component cmd-go. This manipulation causes file inclusion. This vulnerability is tracked as CVE-2025-4674. The attack is only possible within the local network. No exploit exists. It is advisable to upgrade the affected component.

A vulnerability was found in Google Go 1.23/1.24. It has been classified as problematic. This impacts an unknown function of the component net-http. The manipulation leads to http request smuggling. This vulnerability is listed as CVE-2025-22871. The attack may be initiated remotely. There is no available exploit. It is suggested to install a patch to address this issue.

A vulnerability was found in Google Go up to 1.23.6/1.24.0. It has been classified as problematic. This impacts an unknown function of the component IPv6 Zone ID Handler. Performing manipulation results in misinterpretation of input. This vulnerability is cataloged as CVE-2025-22870. The attack must originate from the local network. There is no exploit available. Upgrading the affected component is recommended.

It seems this issue is a false-positive. Please confirm the sources provided and consider disregarding this entry.

This issue is likely a false positive. Please verify the cited sources and consider not including this entry.

A vulnerability was found in linlinjava litemall up to 1.8.0. It has been declared as critical. This affects an unknown function of the file AdminGoodscontroller.java. The manipulation of the argument goodsId/goodsSn/name results in sql injection. This vulnerability is cataloged as CVE-2024-6452. The attack may be launched remotely. Furthermore, there is an exploit available.

A vulnerability identified as critical has been detected in linlinjava litemall up to 1.8.0. Affected by this issue is the function Upload of the file /wx/storage/upload. The manipulation of the argument File leads to unrestricted upload. This vulnerability is referenced as CVE-2025-8764. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

A vulnerability has been found in linlinjava litemall up to 1.8.0 and classified as critical. This affects the function create of the file litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStorageController.java of the component Endpoint. Performing manipulation of the argument File results in unrestricted upload. This vulnerability is cataloged as CVE-2025-8965. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

A vulnerability, which was classified as problematic, has been found in Scada-LTS 2.7.8.1. Affected is an unknown function of the file pointHierarchy/new/. Performing manipulation of the argument Title results in cross site scripting. This vulnerability is reported as CVE-2025-9138. The attack is possible to be carried out remotely. Moreover, an exploit is present. The vendor explains: "[T]he risks of indicated vulnerabilities seem to be minimal as all scenarios likely require admin permissions. Moreover, regardless our team fixes those vulnerabilities - the overall risk change to the user due to malicious admin actions will not be lower. An admin user - by definition - has full control over HTML and JS code that is delivered to users in regular synoptic panels. In other words - due to the design of the system it is not possible to limit the admin user to attack the users."

A vulnerability, which was classified as problematic, was found in Scada-LTS 2.7.8.1. Affected by this vulnerability is an unknown functionality of the file /Scada-LTS/dwr/call/plaincall/WatchListDwr.init.dwr. Executing manipulation can lead to information disclosure. This vulnerability appears as CVE-2025-9139. The attack may be performed from remote. In addition, an exploit is available. The vendor explains: "[T]he risks of indicated vulnerabilities seem to be minimal as all scenarios likely require admin permissions. Moreover, regardless our team fixes those vulnerabilities - the overall risk change to the user due to malicious admin actions will not be lower."

A vulnerability was found in Scada-LTS 2.7.8.1 and classified as problematic. This affects an unknown part of the file mailing_lists.shtm. The manipulation of the argument name/userList/address results in cross site scripting. This vulnerability is known as CVE-2025-9143. It is possible to launch the attack remotely. Furthermore, an exploit is available.

A vulnerability was found in Scada-LTS 2.7.8.1. It has been classified as problematic. This vulnerability affects unknown code of the file publisher_edit.shtm. This manipulation of the argument Name causes cross site scripting. This vulnerability is handled as CVE-2025-9144. The attack can be initiated remotely. Additionally, an exploit exists.

A vulnerability classified as problematic has been found in linlinjava litemall up to 1.8.0. Affected by this issue is some unknown functionality of the file litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/util/JwtHelper.java of the component JSON Web Token Handler. This manipulation of the argument SECRET with the input X-Litemall-Token causes hard-coded credentials. The identification of this vulnerability is CVE-2025-8974. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

A vulnerability, which was classified as problematic, was found in Scada-LTS up to 2.7.8.1. This impacts an unknown function of the file usersProfiles.shtm. The manipulation of the argument Username results in cross site scripting. This vulnerability is known as CVE-2025-7729. It is possible to launch the attack remotely. Furthermore, an exploit is available. The vendor was contacted early about this issue and confirmed that it will be fixed in the upcoming release 2.8.0.