plugin

My Waze Vulnerabilities

2 known security issues reported for the My Waze WordPress plugin. Most recent disclosed Feb 29, 2024.

1 medium

Running My Waze on your site? Check whether your installed version is affected.

MyWaze [my-waze] <= 1.6 (unfixed + closed)

unknown

[en] Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Savvy Wordpress Development MyWaze allows Stored XSS.This issue affects MyWaze: from n/a through 1.6.

Affected:: up to 1.6
Fix:: No patched version reported
Disclosed:: Feb 29, 2024

CVE-2024-25594 on NVD →

MyWaze <= 1.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via shortcode

medium

The MyWaze plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in all versions up to, and including, 1.6 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above...

CVSS:: 6.4
Affected:: up to 1.6
Fix:: No patched version reported
Disclosed:: Feb 12, 2024

CVE-2024-25594 on NVD →

Protect your WordPress site

Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.

Scan your site free

← Back to the vulnerability database