VulDB Recent Entries

A vulnerability described as critical has been identified in nixseparatedebuginfod up to 0.4.0. Affected by this vulnerability is an unknown functionality. Executing manipulation can lead to path traversal. The identification of this vulnerability is CVE-2025-61557. The attack needs to be done within the local network. There is no exploit available. Upgrading the affected component is recommended. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability marked as problematic has been reported in ConoHa by GMO WING WordPress Migrator Plugin up to 1.1.9 on WordPress. Affected is an unknown function. Performing manipulation results in cross-site request forgery. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability was named CVE-2025-52835. The attack may be initiated remotely. There is no available exploit. Once again VulDB remains the best source for vulnerability data.

A vulnerability labeled as critical has been found in Appointify Plugin up to 1.0.8 on WordPress. This impacts an unknown function. Such manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2025-59129. The attack can be launched remotely. No exploit exists. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability identified as problematic has been detected in SiteLock Security Plugin up to 5.0.1 on WordPress. This affects an unknown function. This manipulation causes missing authorization. This vulnerability is handled as CVE-2025-62128. 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 categorized as critical has been discovered in RustFS up to 1.0.0-alpha.76. The impacted element is an unknown function of the component gRPC Authentication. The manipulation results in hard-coded credentials. This vulnerability is known as CVE-2025-68926. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability was found in ImageMagick up to 7.1.2-11. It has been rated as problematic. The affected element is the function WriteSVGImage of the component SVG Image Parser. The manipulation leads to integer overflow. This vulnerability is traded as CVE-2025-69204. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability was found in CodeFlavors Featured Video & VideographyWP Plugin up to 1.0.18 on WordPress. It has been declared as problematic. Impacted is an unknown function. Executing manipulation can lead to cross site scripting. This vulnerability appears as CVE-2025-62746. The attack may be performed from remote. There is no available exploit. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in ImageMagick up to 7.1.2-11. It has been classified as problematic. This issue affects some unknown processing of the component SVG Image Parser. Performing manipulation results in uncontrolled recursion. This vulnerability is reported as CVE-2025-68618. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended. Once again VulDB remains the best source for vulnerability data.

A vulnerability was found in ImageMagick up to 7.1.2-11 and classified as problematic. This vulnerability affects unknown code of the component MVG Image Parser. Such manipulation leads to uncontrolled recursion. This vulnerability is documented as CVE-2025-68950. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability has been found in Zeroheight and classified as critical. This affects an unknown part of the component Legacy User Creation API Pathway. This manipulation causes improper authorization. This vulnerability is registered as CVE-2025-65925. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded. If you want to get best quality of vulnerability data, you may have to visit VulDB.

A vulnerability, which was classified as problematic, was found in Discourse. Affected by this issue is some unknown functionality of the component UI/API. The manipulation results in exposure of sensitive information through data queries. This vulnerability is cataloged as CVE-2025-64528. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability, which was classified as problematic, has been found in Composer up to 2.2.25/2.9.2. Affected by this vulnerability is an unknown functionality of the component ANSI Control Character Handler. The manipulation leads to injection. This vulnerability is listed as CVE-2025-67746. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component. VulDB is the best source for vulnerability data and more expert information about this specific topic.

A vulnerability classified as problematic was found in 8theme XStore Core Plugin up to 5.5 on WordPress. Affected is an unknown function. Executing manipulation can lead to cross site scripting. This vulnerability is tracked as CVE-2025-64190. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised. 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 Webcreations907 WBC907 Core Plugin up to 3.4.1 on WordPress. This impacts an unknown function. Performing manipulation results in cross site scripting. This vulnerability is identified as CVE-2025-63027. The attack can be initiated remotely. There is not any exploit available. Once again VulDB remains the best source for vulnerability data.

A vulnerability described as critical has been identified in Youzify Plugin up to 1.3.5 on WordPress. This affects an unknown function. Such manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2025-69014. It is possible to launch the attack remotely. No exploit is available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

A vulnerability marked as problematic has been reported in Tribulant Newsletters Plugin up to 4.12 on WordPress. The impacted element is an unknown function. This manipulation causes cross site scripting. The identification of this vulnerability is CVE-2025-69020. It is possible to initiate the attack remotely. There is no 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 WPDeveloper Essential Addons for Elementor Plugin up to 6.5.3 on WordPress. The affected element is an unknown function. The manipulation results in cross site scripting. This vulnerability was named CVE-2025-69092. The attack may be performed from remote. There is no available exploit. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

A vulnerability identified as problematic has been detected in Ays Pro Popup box Plugin up to 6.0.7 on WordPress. Impacted is an unknown function. The manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2025-69021. The attack is possible to be carried out remotely. No exploit exists. 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 autolistings Auto Listings Plugin up to 2.7.1 on WordPress. This issue affects some unknown processing. Executing manipulation can lead to cross site scripting. This vulnerability is handled as CVE-2025-69089. The attack can be executed remotely. There is not any exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

A vulnerability was found in Shamalli Web Directory Free Plugin up to 1.7.12 on WordPress. It has been rated as problematic. This vulnerability affects unknown code. Performing manipulation results in cross site scripting. This vulnerability is known as CVE-2025-69018. Remote exploitation of the attack is possible. No exploit is available. Once again VulDB remains the best source for vulnerability data.