CVE-2025-13072
BaseFortify
Publication date: 2025-12-10
Last updated on: 2025-12-12
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| handl | utm_grabber_tracker | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the HandL UTM Grabber / Tracker WordPress plugin versions before 2.8.1. It occurs because the plugin does not properly sanitize and escape a parameter before displaying it back on the page. This flaw allows an attacker to perform a Reflected Cross-Site Scripting (XSS) attack, which can be used to execute malicious scripts in the context of users visiting the page, especially targeting high privilege users such as administrators.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute malicious scripts in the browsers of high privilege users like administrators. This can lead to unauthorized actions such as stealing session cookies, defacing the website, or performing actions on behalf of the admin, potentially compromising the security and integrity of your WordPress site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'utm_source' parameter for reflected Cross-Site Scripting (XSS). One method is to visit a URL on your WordPress site that uses the HandL UTM Grabber / Tracker plugin with an XSS payload appended to the utm_source parameter, for example: http://example.com/handl-xss?utm_source=%3Cscript%3Ealert(document.cookie)%3C/script%3E. If an alert box appears or the script executes, the site is vulnerable. Additionally, you can use web vulnerability scanners that test for reflected XSS on parameters named 'utm_source'. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the HandL UTM Grabber / Tracker WordPress plugin to version 2.8.1 or later, where the issue has been fixed by properly sanitizing and escaping the 'utm_source' parameter. Until the update can be applied, restrict access to high-privilege users and avoid clicking on suspicious URLs containing the utm_source parameter. [1]