Vuldb Updates

A vulnerability identified as critical has been detected in Magic Import Document Extractor Plugin up to 1.0.4 on WordPress. The impacted element is the function ajax_sync_usage. Performing a manipulation results in missing authorization. This vulnerability is identified as CVE-2025-15507. The attack can be initiated remotely. There is not any exploit available.

A vulnerability labeled as problematic has been found in WebPurify Profanity Filter Plugin up to 4.0.2 on WordPress. This affects the function webpurify_save_options of the component Setting Handler. Executing a manipulation can lead to missing authorization. This vulnerability is tracked as CVE-2026-0572. The attack can be launched remotely. No exploit exists.

A vulnerability marked as critical has been reported in Code Explorer Plugin up to 1.4.6 on WordPress. This impacts an unknown function. The manipulation of the argument File leads to path traversal. This vulnerability is listed as CVE-2025-15487. The attack may be initiated remotely. There is no available exploit.

A vulnerability classified as problematic has been found in Extended Random Number Generator Plugin up to 1.1 on WordPress. Affected by this vulnerability is an unknown functionality of the component Setting Handler. This manipulation causes cross site scripting. This vulnerability is registered as CVE-2026-0681. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability classified as problematic was found in Smart Appointment & Booking Plugin up to 1.0.7 on WordPress. Affected by this issue is the function saab_save_form_data. Such manipulation leads to cross site scripting. This vulnerability is documented as CVE-2026-0742. The attack can be executed remotely. There is not any exploit available.

A vulnerability was found in Themeisle Menu Icons Plugin up to 0.13.20 on WordPress. It has been rated as problematic. This vulnerability affects the function _wp_attachment_image_alt. The manipulation leads to cross site scripting. This vulnerability is listed as CVE-2026-1755. The attack may be initiated remotely. There is no available exploit.

A vulnerability marked as critical has been reported in bolo-blog bolo-solo up to 2.6.4. The impacted element is the function unpackFilteredZip of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component ZIP File Handler. Performing a manipulation of the argument File results in path traversal. This vulnerability is reported as CVE-2026-1810. The attack is possible to be carried out remotely. Moreover, an exploit is present. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability classified as critical has been found in bolo-blog bolo-solo up to 2.6.4. This impacts the function importFromCnblogs of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. The manipulation of the argument File leads to path traversal. This vulnerability is traded as CVE-2026-1812. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was found in Xendit Payment Plugin up to 6.0.2 on WordPress. It has been classified as problematic. Affected by this vulnerability is the function wc_xendit_callback of the component POST Handler. Performing a manipulation results in missing authorization. This vulnerability was named CVE-2025-14461. The attack may be initiated remotely. There is no available exploit.

A vulnerability classified as critical was found in bolo-blog bolo-solo up to 2.6.4. Affected is an unknown function of the file src/main/java/org/b3log/solo/bolo/pic/PicUploadProcessor.java of the component FreeMarker Template Handler. The manipulation of the argument File results in unrestricted upload. This vulnerability is known as CVE-2026-1813. It is possible to launch the attack remotely. Furthermore, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability described as critical has been identified in bolo-blog bolo-solo up to 2.6.4. This affects the function importFromMarkdown of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. Executing a manipulation of the argument File can lead to path traversal. This vulnerability appears as CVE-2026-1811. The attack may be performed from remote. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability, which was classified as problematic, has been found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. The impacted element is an unknown function of the file /proc/driver/unifi0/send_delts of the component Wi-Fi Driver. This manipulation causes uncontrolled memory allocation. This vulnerability is registered as CVE-2025-58340. The attack requires access to the local network. No exploit is available.

A vulnerability, which was classified as problematic, was found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. This affects an unknown function of the file /proc/driver/unifi0/ap_cert_disable_ht_vht of the component Wi-Fi Driver. Such manipulation leads to uncontrolled memory allocation. This vulnerability is documented as CVE-2025-58341. The attack requires being on the local network. There is not any exploit available.

A vulnerability has been found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200 and classified as problematic. This impacts an unknown function of the file /proc/driver/unifi0/uapsd of the component Wi-Fi Driver. Performing a manipulation results in uncontrolled memory allocation. This vulnerability is reported as CVE-2025-58342. The attacker must have access to the local network to execute the attack. No exploit exists.

A vulnerability was found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200 and classified as problematic. Affected is an unknown function of the file /proc/driver/unifi0/create_tspec of the component Wi-Fi Driver. Executing a manipulation can lead to uncontrolled memory allocation. This vulnerability appears as CVE-2025-58343. The attacker needs to be present on the local network. There is no available exploit.

A vulnerability was found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the file /proc/driver/unifi0/conn_log_event_burst_to_us of the component Wi-Fi Driver. The manipulation leads to uncontrolled memory allocation. This vulnerability is traded as CVE-2025-58344. Access to the local network is required for this attack to succeed. There is no exploit available.

A vulnerability was found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. It has been declared as problematic. Affected by this issue is some unknown functionality of the file /proc/driver/unifi0/ap_certif_11ax_mode of the component Wi-Fi Driver. The manipulation results in uncontrolled memory allocation. This vulnerability is known as CVE-2025-58345. Access to the local network is required for this attack. No exploit is available.

A vulnerability was found in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. It has been rated as problematic. This affects an unknown part of the file /proc/driver/unifi0/send_addts of the component Wi-Fi Driver. This manipulation causes uncontrolled memory allocation. This vulnerability is handled as CVE-2025-58346. The attack can only be done within the local network. There is not any exploit available.

A vulnerability categorized as problematic has been discovered in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. This vulnerability affects unknown code of the file /proc/driver/unifi0/p2p_certif of the component Wi-Fi Driver. Such manipulation leads to uncontrolled memory allocation. This vulnerability is uniquely identified as CVE-2025-58347. The attack can only be initiated within the local network. No exploit exists.

A vulnerability identified as problematic has been detected in Samsung Mobile Processor and Wearable Processor Exynos up to 2200. This issue affects some unknown processing of the file /proc/driver/unifi0/confg_tspec of the component Wi-Fi Driver. Performing a manipulation results in uncontrolled memory allocation. This vulnerability was named CVE-2025-58348. The attack needs to be approached within the local network. There is no available exploit.