WP-Safety
CVE-2026-57351

HandL UTM Grabber / Tracker <= 2.9.2 - Unauthenticated Stored Cross-Site Scripting

highImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
7.2
CVSS Score
7.2
CVSS Score
high
Severity
2.9.3
Patched in
7d
Time to patch

Description

The HandL UTM Grabber / Tracker plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.9.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS Vector Breakdown

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Low
Confidentiality
Low
Integrity
None
Availability

Technical Details

Affected versions<=2.9.2
PublishedJuly 1, 2026
Last updatedJuly 7, 2026
Affected pluginhandl-utm-grabber

What Changed in the Fix

Changes introduced in v2.9.3

Loading patch diff...

Source Code

WordPress.org SVN
Vulnerable v2.9.2
Browse source Download .zip
Patched v2.9.3
Browse source Download .zip
Research Plan
Unverified

# Research Plan: CVE-2026-57351 - HandL UTM Grabber / Tracker Stored XSS ## 1. Vulnerability Summary The **HandL UTM Grabber / Tracker** plugin (up to 2.9.2) is vulnerable to **Unauthenticated Stored Cross-Site Scripting (XSS)**. The vulnerability exists because the plugin captures user-controlled …

Show full research plan

Research Plan: CVE-2026-57351 - HandL UTM Grabber / Tracker Stored XSS

1. Vulnerability Summary

The HandL UTM Grabber / Tracker plugin (up to 2.9.2) is vulnerable to Unauthenticated Stored Cross-Site Scripting (XSS). The vulnerability exists because the plugin captures user-controlled input from HTTP headers (like X-Forwarded-For) and URL parameters, stores them in browser cookies without sufficient validation, and subsequently processes these values unsafely. Specifically, while some shortcodes use esc_html(), other integration points—such as the Ninja Forms Merge Tags—use urldecode() on raw cookie data without escaping, and the Admin Analytics dashboard (rendered via React) likely displays tracked UTM data without proper output encoding.

2. Attack Vector Analysis

  • Endpoint: Any frontend page of the WordPress site.
  • Hook: init (via the CaptureUTMs function).
  • Vulnerable Parameters:
    • utm_source, utm_medium, utm_term, utm_content, utm_campaign, gclid (via URL parameters or Cookie header).
    • handl_ip (via X-Forwarded-For HTTP header).
    • handl_url / handl_landing_page (via the Request URI).
  • Authentication: None (
References
https://www.wordfence.com/threat-intel/vulnerabilities/id/f324b272-1e2f-4951-a8ae-5210a8d4dcbd?source=api-prod

Check if your site is affected.

Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.

Run free audit Browse CVE database