Vuldb Updates

A vulnerability identified as problematic has been detected in Discourse. Affected by this issue is the function top_uploads of the component Admin Report. The manipulation leads to incorrect authorization. This vulnerability is traded as CVE-2025-69218. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

A vulnerability labeled as problematic has been found in Discourse. This affects an unknown part of the component Private Message Handler. The manipulation results in incorrect authorization. This vulnerability is known as CVE-2025-68933. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.

A vulnerability classified as problematic was found in Discourse. This impacts an unknown function. The manipulation results in incorrect authorization. This vulnerability was named CVE-2025-69289. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.

A vulnerability marked as problematic has been reported in Discourse. This impacts an unknown function of the component 404 Page Search Box. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2026-23743. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

A vulnerability classified as problematic has been found in Free5GC SMF up to 4.1.0. Affected by this vulnerability is the function HandlePfcpSessionReportRequest of the file internal/pfcp/handler/handler.go of the component PFCP. The manipulation leads to denial of service. This vulnerability is referenced as CVE-2026-1683. Remote exploitation of the attack is possible. Furthermore, an exploit is available. To fix this issue, it is recommended to deploy a patch.

A vulnerability classified as problematic was found in Free5GC SMF up to 4.1.0. Affected by this issue is the function HandleReports of the file /internal/context/pfcp_reports.go of the component PFCP UDP Endpoint. The manipulation results in denial of service. This vulnerability is identified as CVE-2026-1684. The attack can be executed remotely. There is not any exploit available. It is advisable to implement a patch to correct this issue.

A vulnerability identified as problematic has been detected in Codriapp Innovation and Software HeyGarson up to 30012026. Affected is an unknown function. Performing a manipulation results in information exposure through error message. This vulnerability is known as CVE-2025-1395. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability described as problematic has been identified in Free5GC SMF up to 4.1.0. Affected is the function HandlePfcpAssociationReleaseRequest of the file internal/pfcp/handler/handler.go of the component PFCP UDP Endpoint. Executing a manipulation can lead to null pointer dereference. The identification of this vulnerability is CVE-2026-1682. The attack may be launched remotely. Furthermore, there is an exploit available. A patch should be applied to remediate this issue.

A vulnerability identified as problematic has been detected in Discourse. The affected element is the function authorized_extensions. This manipulation causes escaping of output. This vulnerability is handled as CVE-2025-66488. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

A vulnerability classified as critical has been found in Discourse. Affected is an unknown function of the component Subscription Handler. The manipulation leads to missing authorization. This vulnerability is referenced as CVE-2025-68479. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic was found in Discourse. Affected by this vulnerability is an unknown functionality of the file /u//preferences/username of the component Username Preference Endpoint. The manipulation results in allocation of resources. This vulnerability is identified as CVE-2025-68659. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

A vulnerability labeled as critical has been found in Sangfor Operation and Maintenance Security Management System up to 3.0.12. The impacted element is an unknown function of the file /fort/audit/get_clip_img of the component HTTP POST Request Handler. Such manipulation of the argument frame/dirno leads to command injection. This vulnerability is referenced as CVE-2026-1412. It is possible to launch the attack remotely. Furthermore, an exploit is available.

A vulnerability marked as critical has been reported in Sangfor Operation and Maintenance Security Management System up to 3.0.12. This affects the function portValidate of the file /fort/ip_and_port/port_validate of the component HTTP POST Request Handler. Performing a manipulation of the argument port results in command injection. This vulnerability is identified as CVE-2026-1413. The attack can be initiated remotely. Additionally, an exploit exists.

A vulnerability described as critical has been identified in Sangfor Operation and Maintenance Security Management System up to 3.0.12. This impacts the function getInformation of the file /equipment/get_Information of the component HTTP POST Request Handler. Executing a manipulation of the argument fortEquipmentIp can lead to command injection. This vulnerability is tracked as CVE-2026-1414. The attack can be launched remotely. Moreover, an exploit is present.

A vulnerability labeled as critical has been found in D-Link DCS700l 1.03.09. Affected is an unknown function of the file /setDayNightMode of the component Web Form Handler. Executing a manipulation of the argument LightSensorControl can lead to command injection. The identification of this vulnerability is CVE-2026-1419. The attack may be launched remotely. Furthermore, there is an exploit available.

A vulnerability was found in Beetel 777VR1 up to 01.00.09/01.00.09_55. It has been declared as critical. This vulnerability affects unknown code of the component UART Interface. Executing a manipulation can lead to weak password requirements. This vulnerability is handled as CVE-2026-1408. The physical device can be targeted for the attack. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Beetel 777VR1 up to 01.00.09/01.00.09_55. It has been rated as problematic. This issue affects some unknown processing of the component UART Interface. The manipulation leads to improper restriction of excessive authentication attempts. This vulnerability is uniquely identified as CVE-2026-1409. It is possible to launch the attack on the physical device. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Beetel 777VR1 up to 01.00.09/01.00.09_55. It has been classified as problematic. This affects an unknown part of the component UART Interface. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2026-1407. The attack may be carried out on the physical device. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability described as problematic has been identified in Autodesk Fusion 2604.1.25. Affected by this issue is some unknown functionality of the component HTML Handler. The manipulation results in HTML injection. This vulnerability is cataloged as CVE-2026-0533. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.

A vulnerability classified as problematic has been found in Autodesk Fusion 2604.1.25. This affects an unknown part of the component HTML Handler. This manipulation causes HTML injection. This vulnerability is registered as CVE-2026-0534. The attack needs to be launched locally. No exploit is available. It is recommended to upgrade the affected component.