Filtered by vendor Hasthemes
Subscriptions
Total
40 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-23899 | 1 Hasthemes | 1 Extensions For Cf7 | 2024-08-02 | 4.3 Medium |
| Cross-Site Request Forgery (CSRF) vulnerability in HasThemes Extensions For CF7 plugin <= 2.0.8 versions leads to arbitrary plugin activation. | ||||
| CVE-2023-23801 | 1 Hasthemes | 1 Really Simple Google Tag Manager | 2024-08-02 | 4.3 Medium |
| Cross-Site Request Forgery (CSRF) vulnerability in HasThemes Really Simple Google Tag Manager plugin <= 1.0.6 versions. | ||||
| CVE-2023-1086 | 1 Hasthemes | 1 Preview Link Generator | 2024-08-02 | 4.3 Medium |
| The Preview Link Generator WordPress plugin before 1.0.4 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-1087 | 1 Hasthemes | 1 Wc Sales Notification | 2024-08-02 | 4.3 Medium |
| The WC Sales Notification WordPress plugin before 1.2.3 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-1089 | 1 Hasthemes | 1 Coupon Zen | 2024-08-02 | 4.3 Medium |
| The Coupon Zen WordPress plugin before 1.0.6 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-1088 | 1 Hasthemes | 1 Wp Plugin Manager | 2024-08-02 | 4.3 Medium |
| The WP Plugin Manager WordPress plugin before 1.1.8 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0504 | 1 Hasthemes | 1 Ht Politic | 2024-08-02 | 4.3 Medium |
| The HT Politic WordPress plugin before 2.3.8 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0495 | 1 Hasthemes | 1 Ht Slider For Elementor | 2024-08-02 | 4.3 Medium |
| The HT Slider For Elementor WordPress plugin before 1.4.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0501 | 1 Hasthemes | 1 Wp Insurance | 2024-08-02 | 6.5 Medium |
| The WP Insurance WordPress plugin before 2.1.4 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0505 | 1 Hasthemes | 1 Ever Compare | 2024-08-02 | 4.3 Medium |
| The Ever Compare WordPress plugin through 1.2.3 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0502 | 1 Hasthemes | 1 Wp News | 2024-08-02 | 6.5 Medium |
| The WP News WordPress plugin through 1.1.9 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0484 | 1 Hasthemes | 1 Contact Form 7 Widget For Elementor Page Builder \& Gutenberg Blocks | 2024-08-02 | 4.3 Medium |
| The Contact Form 7 Widget For Elementor Page Builder & Gutenberg Blocks WordPress plugin before 1.1.6 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0496 | 1 Hasthemes | 1 Ht Event | 2024-08-02 | 4.3 Medium |
| The HT Event WordPress plugin before 1.4.6 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0500 | 1 Hasthemes | 1 Wp Film Studio | 2024-08-02 | 6.5 Medium |
| The WP Film Studio WordPress plugin before 1.3.5 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0498 | 1 Hasthemes | 1 Wp Education | 2024-08-02 | 4.3 Medium |
| The WP Education WordPress plugin before 1.2.7 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0503 | 1 Hasthemes | 1 Free Woocommerce Theme 99fy Extension | 2024-08-02 | 4.3 Medium |
| The Free WooCommerce Theme 99fy Extension WordPress plugin before 1.2.8 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0497 | 1 Hasthemes | 1 Ht Portfolio | 2024-08-02 | 4.3 Medium |
| The HT Portfolio WordPress plugin before 1.1.6 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0499 | 1 Hasthemes | 1 Quickswish | 2024-08-02 | 4.3 Medium |
| The QuickSwish WordPress plugin before 1.1.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack | ||||
| CVE-2023-0231 | 1 Hasthemes | 1 Shoplentor | 2024-08-02 | 5.4 Medium |
| The ShopLentor WordPress plugin before 2.5.4 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. | ||||
| CVE-2023-0232 | 1 Hasthemes | 1 Shoplentor | 2024-08-02 | 9.8 Critical |
| The ShopLentor WordPress plugin before 2.5.4 unserializes user input from cookies in order to track viewed products and user data, which could lead to PHP Object Injection. | ||||