LiveActive security incident?Get immediate response
CVE Record

CVE-2024-25594: WordPress MyWaze Plugin <= 1.6 is vulnerable to Cross Site Scripting (XSS)

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-25594 is a stored cross-site scripting issue in the WordPress MyWaze plugin through version 1.6. A lower-privileged authenticated user may be able to store script content that later runs in another user’s browser, creating risk to site trust, user sessions, and displayed content.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It is not evidenced as actively exploited in the supplied sources, but stored XSS can affect site integrity and user trust. Prioritize internet-facing or multi-user WordPress sites first.

Technical view

The CVE describes CWE-79 improper neutralization during web page generation in Savvy Wordpress Development MyWaze. It affects the WordPress package my-waze through version 1.6. CVSS 3.1 is 6.5, with network access, low attack complexity, low privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is likely limited to WordPress sites running MyWaze version 1.6 or earlier. Risk is higher where untrusted or low-privileged users can access the vulnerable input path and where administrators or visitors later view stored content.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires low privileges and user interaction, consistent with stored XSS that must be saved first and later rendered to a victim.

Researcher notes

Evidence identifies stored XSS but does not provide a fixed version, exploit details, or affected endpoint in the supplied bundle. Avoid assuming patch availability. Validation should focus on plugin presence, version, reachable input surfaces, and whether untrusted roles can store rendered content.

Mitigation direction

  • Inventory WordPress sites for the MyWaze plugin and installed version.
  • Review vendor or Patchstack guidance for a fixed release or official workaround.
  • Disable or remove MyWaze where business use is not required.
  • Restrict plugin access to trusted users until remediation is confirmed.
  • Monitor affected sites for unexpected scripts or content changes.

Validation and detection

  • Confirm whether any site runs MyWaze version 1.6 or earlier.
  • Review WordPress roles allowed to submit or edit MyWaze-controlled content.
  • Inspect rendered plugin output for unsafe script execution indicators.
  • Check security logs for suspicious plugin-related content changes.
  • Document remediation status for every affected WordPress instance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-25594 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2024-25594Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Savvy Wordpress DevelopmentMyWazemy-waze, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.