Dwbooster
18 vulnerabilities.
All published vulnerabilities with a CVE number in Dwbooster products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2024-13758 | Dwbooster Cp Contact Form: The CP Contact Form with PayPal plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.52. This … | 2025-01-30 | 6.5 |
| CVE-2023-41732 | Dwbooster Cp Blocks: Cross-Site Request Forgery (CSRF) vulnerability in CodePeople CP Blocks plugin <= 1.0.20 versions. | 2023-10-06 | 5.4 |
| CVE-2023-6446 | Dwbooster Calculated Fields Form: The Calculated Fields Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and … | 2024-01-11 | 4.4 |
| CVE-2022-41692 | Dwbooster Appointment Hour Booking: Missing Authorization vulnerability in Appointment Hour Booking plugin <= 1.3.71 on WordPress. | 2022-11-18 | 4.3 |
| CVE-2022-4036 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking plugin for WordPress is vulnerable to CAPTCHA bypass in versions up to, and including, 1.3.72. This is due to the use … | 2022-11-29 | 5.3 |
| CVE-2022-4035 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking plugin for WordPress is vulnerable to iFrame Injection via the ‘email’ or general field parameters in versions up to, … | 2022-11-29 | 7.2 |
| CVE-2022-4034 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking Plugin for WordPress is vulnerable to CSV Injection in versions up to, and including, 1.3.72. This makes it possible … | 2022-11-29 | 5.8 |
| CVE-2022-3427 | Dwbooster Corner Ad: The Corner Ad plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.56. This is due to missing or … | 2022-12-15 | 8.8 |
| CVE-2022-2846 | Dwbooster Calendar Event Multi View: The Calendar Event Multi View WordPress plugin before 1.4.07 does not have any authorisation and CSRF checks in place when creating an event, and … | 2022-08-16 | 4.3 |
| CVE-2022-2169 | Dwbooster Loading Page With Loading Screen: The Loading Page with Loading Screen WordPress plugin before 1.0.83 does not escape its settings, allowing high privilege users such as admin to … | 2022-07-17 | 4.8 |
| CVE-2022-1710 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking WordPress plugin before 1.3.56 does not sanitise and escape a settings of its Calendar fields, which could allow high … | 2022-06-13 | 4.8 |
| CVE-2022-1692 | Dwbooster Cp Image Store With Slideshow: The CP Image Store with Slideshow WordPress plugin before 1.0.68 does not sanitise and escape the ordering_by query parameter before using it in a … | 2022-06-08 | 9.8 |
| CVE-2022-0448 | Dwbooster Cp Blocks: The CP Blocks WordPress plugin before 1.0.15 does not sanitise and escape its "License ID" settings, which could allow high privilege users to … | 2022-03-07 | 4.8 |
| CVE-2021-24712 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking WordPress plugin before 1.3.17 does not properly sanitize values used when creating new calendars. | 2021-10-11 | 5.4 |
| CVE-2021-24673 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking WordPress plugin before 1.3.16 does not escape some of the Calendar Form settings, allowing high privilege users to … | 2021-10-04 | 4.8 |
| CVE-2021-24498 | Dwbooster Calendar Event Multi View: The Calendar Event Multi View WordPress plugin before 1.4.01 does not sanitise or escape the 'start' and 'end' GET parameters before outputting … | 2021-08-02 | 6.1 |
| CVE-2019-13505 | Dwbooster Appointment Hour Booking: The Appointment Hour Booking plugin 1.1.44 for WordPress allows XSS via the E-mail field, as demonstrated by email_1. | 2019-07-11 | 6.1 |
| CVE-2017-18579 | Dwbooster Corner Ad: The corner-ad plugin before 1.0.8 for WordPress has XSS. | 2019-08-22 | 6.1 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.