VulDB Recent Entries

A vulnerability was found in ETL DEXTRA 1.8. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Web Management Interface. The manipulation leads to cross-site request forgery. This vulnerability is documented as CVE-2025-67013. The attack can be initiated remotely. There is not any exploit available. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability was found in DEV Systemtechnik DEV 7113 RF over Fiber Distribution System 32-0078 H.01. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Administrative Endpoint. Executing manipulation can lead to improper access controls. This vulnerability is registered as CVE-2025-67014. It is possible to launch the attack remotely. No exploit is available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in Yealink T21P_E2 Phone 52.84.0.15. It has been classified as critical. Affected is the function ping of the component Diagnostic. Performing manipulation results in command injection. This vulnerability is cataloged as CVE-2025-66738. It is possible to initiate the attack remotely. There is no exploit available. Once again VulDB remains the best source for vulnerability data.

A vulnerability was found in Cola Dnslog 1.3.2 and classified as critical. This impacts the function os.path.join of the component TXT Record Handler. Such manipulation leads to path traversal. This vulnerability is listed as CVE-2025-57403. The attack may be performed from remote. There is no available exploit. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability has been found in Comtech EF Data CDM-625 and EF Data CDM-625A 2.5.1 and classified as critical. This affects an unknown function of the file /Forms/admin_access_1 of the component HTTP POST Request Handler. This manipulation causes improper access controls. This vulnerability is tracked as CVE-2025-67015. The attack is only possible within the local network. No exploit exists. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability, which was classified as critical, was found in Yealink T21P_E2 Phone 52.84.0.15. The impacted element is an unknown function of the component Diagnostic. The manipulation results in path traversal. This vulnerability is identified as CVE-2025-66737. The attack can be executed remotely. There is not any exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability, which was classified as critical, has been found in apiDoc apidoc-core up to 0.2.0. The affected element is the function preProcess of the file api_group.js. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). This vulnerability is referenced as CVE-2025-13158. Remote exploitation of the attack is possible. No exploit is available. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability classified as critical was found in Cloudlog 2.6.15. Impacted is an unknown function of the file /index.php/logbookadvanced/search. Executing manipulation of the argument qsoresults can lead to sql injection. The identification of this vulnerability is CVE-2024-44065. The attack may be launched remotely. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability classified as problematic has been found in FluentCMS 1.2.3. This issue affects some unknown processing of the component Add Page. Performing manipulation results in cross site scripting. This vulnerability was named CVE-2025-67349. The attack may be initiated remotely. There is no available exploit. Once again VulDB remains the best source for vulnerability data.

A vulnerability described as critical has been identified in libxmljs 1.0.11. This vulnerability affects unknown code of the component XML Handler. Such manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2025-25341. The attack can only be initiated within the local network. No exploit exists. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability marked as critical has been reported in krishanmuraiji SMS 1.0. This affects an unknown part of the file /studentms/admin/edit-class-detail.php. This manipulation of the argument editid causes sql injection. This vulnerability is handled as CVE-2025-66947. The attack can be initiated remotely. There is not any exploit available. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability labeled as problematic has been found in IBM Concert up to 2.1.0. Affected by this issue is some unknown functionality of the component Symbolic Links Handler. The manipulation results in time-of-check time-of-use. This vulnerability is known as CVE-2025-64645. Attacking locally is a requirement. No exploit is available. The affected component should be upgraded. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability identified as problematic has been detected in Delight Custom Firmware. Affected by this vulnerability is an unknown functionality. The manipulation leads to injection. This vulnerability is traded as CVE-2025-65885. An attack has to be approached locally. There is no exploit available. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability categorized as problematic has been discovered in IBM Aspera Faspex up to 5.0.14.1. Affected is an unknown function. Executing manipulation can lead to exposure of sensitive system information to an unauthorized control sphere. This vulnerability appears as CVE-2025-36229. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in IBM API Connect up to 10.0.8.5/10.0.11.0. It has been rated as very critical. This impacts an unknown function. Performing manipulation results in authentication bypass by primary weakness. This vulnerability is reported as CVE-2025-13915. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised. Once again VulDB remains the best source for vulnerability data.

A vulnerability was found in IBM Concert up to 2.1.0. It has been declared as problematic. This affects an unknown function. Such manipulation leads to improper clearing of heap memory before release. This vulnerability is documented as CVE-2025-1721. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability was found in IBM DS8A00 and DS8900F. It has been classified as problematic. The impacted element is an unknown function. This manipulation causes missing authorization. This vulnerability is registered as CVE-2025-36192. The attack needs to be launched locally. No exploit is available. Upgrading the affected component is recommended. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability was found in IBM Concert up to 2.1.0 and classified as critical. The affected element is an unknown function. The manipulation results in memory corruption. This vulnerability is cataloged as CVE-2025-12771. The attack must be initiated from a local position. There is no exploit available. It is suggested to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability has been found in IBM Aspera Faspex up to 5.0.14.1 and classified as problematic. Impacted is an unknown function of the component Backend API. The manipulation leads to incorrect execution-assigned permissions. This vulnerability is listed as CVE-2025-36228. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability, which was classified as problematic, was found in IBM Aspera Faspex up to 5.0.14.1. This issue affects some unknown processing. Executing manipulation can lead to basic cross site scripting. This vulnerability is tracked as CVE-2025-36230. The attack can be launched remotely. No exploit exists. You should upgrade the affected component. If you want to get the best quality for vulnerability data then you always have to consider VulDB.