Filtered by vendor Themeisle
Subscriptions
Filtered by product Visualizer
Subscriptions
Total
6 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2024-35736 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 8.5 High |
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeisle Visualizer.This issue affects Visualizer: from n/a through 3.11.1. | ||||
CVE-2023-23708 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 6.5 Medium |
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Themeisle Visualizer: Tables and Charts Manager for WordPress plugin <= 3.9.4 versions. | ||||
CVE-2022-46848 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 6.5 Medium |
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Themeisle Visualizer: Tables and Charts Manager for WordPress plugin <= 3.9.1 versions. | ||||
CVE-2022-2444 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 8.8 High |
The Visualizer: Tables and Charts Manager for WordPress plugin for WordPress is vulnerable to deserialization of untrusted input via the 'remote_data' parameter in versions up to, and including 3.7.9. This makes it possible for authenticated attackers with contributor privileges and above to call files using a PHAR wrapper that will deserialize the data and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload. | ||||
CVE-2019-16932 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 10.0 Critical |
A blind SSRF vulnerability exists in the Visualizer plugin before 3.3.1 for WordPress via wp-json/visualizer/v1/upload-data. | ||||
CVE-2019-16931 | 1 Themeisle | 1 Visualizer | 2024-11-21 | 6.1 Medium |
A stored XSS vulnerability in the Visualizer plugin 3.3.0 for WordPress allows an unauthenticated attacker to execute arbitrary JavaScript when an admin or other privileged user edits the chart via the admin dashboard. This occurs because classes/Visualizer/Gutenberg/Block.php registers wp-json/visualizer/v1/update-chart with no access control, and classes/Visualizer/Render/Page/Data.php lacks output sanitization. |
Page 1 of 1.