Vulnerabilities > Iqonic
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-06-08 | CVE-2024-35659 | Unspecified vulnerability in Iqonic Kivicare Authorization Bypass Through User-Controlled Key vulnerability in KiviCare.This issue affects KiviCare: from n/a through 3.6.2. | 8.8 |
| 2023-11-30 | CVE-2023-41128 | Unspecified vulnerability in Iqonic WP Roadmap Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Iqonic Design WP Roadmap – Product Feedback Board allows Stored XSS.This issue affects WP Roadmap – Product Feedback Board: from n/a through 1.0.8. | 4.8 |
| 2023-06-27 | CVE-2023-2623 | Unspecified vulnerability in Iqonic Kivicare The KiviCare WordPress plugin before 3.2.1 does not restrict the information returned in a response and returns all user data, allowing low privilege users such as subscriber to retrieve sensitive information such as the user email and hashed password of other users | 6.5 |
| 2023-06-27 | CVE-2023-2624 | Unspecified vulnerability in Iqonic Kivicare The KiviCare WordPress plugin before 3.2.1 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as administrator | 6.1 |
| 2023-06-27 | CVE-2023-2627 | Unspecified vulnerability in Iqonic Kivicare The KiviCare WordPress plugin before 3.2.1 does not have proper CSRF and authorisation checks in various AJAX actions, allowing any authenticated users, such as subscriber to call them. | 4.3 |
| 2023-06-27 | CVE-2023-2628 | Unspecified vulnerability in Iqonic Kivicare The KiviCare WordPress plugin before 3.2.1 does not have CSRF checks (either flawed or missing completely) in various AJAX actions, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks. | 8.8 |
| 2022-06-13 | CVE-2022-0786 | Unspecified vulnerability in Iqonic Kivicare The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL statements via the ajax_post AJAX action with the get_doctor_details route, leading to SQL Injections exploitable by unauthenticated users | 9.8 |