Codecabin
18 vulnerabilities.
All published vulnerabilities with a CVE number in Codecabin products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2025-24742 | Codecabin Wp Go Maps: Cross-Site Request Forgery (CSRF) vulnerability in WP Go Maps (formerly WP Google Maps) WP Go Maps. This issue affects WP Go Maps: from n/a through … | 2025-01-27 | 4.3 |
| CVE-2024-29931 | Codecabin Wp Go Maps: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Go Maps (formerly WP Google Maps) WP … | 2024-03-27 | 7.1 |
| CVE-2024-13628 | Codecabin Wp Pricing Table: The WP Pricing Table WordPress plugin through 1.1 does not sanitise and escape a parameter before outputting it back in the page, leading to a … | 2025-02-26 | 6.1 |
| CVE-2024-9127 | Codecabin Super Testimonials: The Super Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘alignment’ parameter in all versions up to, and … | 2024-09-26 | 6.4 |
| CVE-2024-5994 | Codecabin Wp Go Maps: The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Custom JS option in versions up to, … | 2024-06-14 | 6.4 |
| CVE-2024-3557 | Codecabin Wp Go Maps: The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpgmza shortcode in all … | 2024-05-24 | 6.4 |
| CVE-2024-1582 | Codecabin Wp Go Maps: The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wpgmza' shortcode in … | 2024-03-13 | 6.4 |
| CVE-2023-6777 | Codecabin Wp Go Maps: The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to unauthenticated API key disclosure in versions up to, and including, … | 2024-04-09 | 5.3 |
| CVE-2023-6627 | Codecabin Wp Go Maps: The WP Go Maps (formerly WP Google Maps) WordPress plugin before 9.0.28 does not properly protect most of its REST API routes, which attackers can … | 2024-01-08 | 6.1 |
| CVE-2023-4839 | Codecabin Wp Go Maps: The WP Go Maps for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 9.0.32 due to … | 2024-03-13 | 4.4 |
| CVE-2022-47595 | Codecabin Wp Go Maps: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP Go Maps (formerly WP Google Maps) plugin <= … | 2023-03-14 | 4.9 |
| CVE-2021-36871 | Codecabin Wp Go Maps: Multiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps Pro premium plugin (versions <= 8.1.11). … | 2021-09-09 | 5.5 |
| CVE-2021-36870 | Codecabin Wp Go Maps: Multiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps plugin (versions <= 8.1.12). Vulnerable … | 2021-09-09 | 5.5 |
| CVE-2021-24383 | Codecabin Wp Go Maps: The WP Google Maps WordPress plugin before 8.1.12 did not sanitise, validate of escape the Map Name when output in the Map List of the admin … | 2021-06-21 | 5.4 |
| CVE-2019-14792 | Codecabin Wp Go Maps: The WP Google Maps plugin before 7.11.35 for WordPress allows XSS via the wp-admin/ rectangle_name or rectangle_opacity parameter. | 2019-08-09 | 5.4 |
| CVE-2019-10692 | Codecabin Wp Go Maps: In the wp-google-maps plugin before 7.11.18 for WordPress, includes/class.rest-api.php in the REST API does not sanitize field names before a … | 2019-04-02 | 9.8 |
| CVE-2019-9912 | Codecabin Wp Go Maps: The wp-google-maps plugin before 7.10.43 for WordPress has XSS via the wp-admin/admin.php PATH_INFO. | 2019-03-21 | 6.1 |
| CVE-2014-7182 | Codecabin Wp Go Maps: Multiple cross-site scripting (XSS) vulnerabilities in the WP Google Maps plugin before 6.0.27 for WordPress allow remote attackers to inject … | 2014-10-22 | 4.3 |
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.