6.1
MEDIUM CVSS 3.1
CVE-2026-3572
iTracker360 <= 2.2.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'itracker_license' Settings Field
Description

The iTracker360 plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in all versions up to and including 2.2.0. This is due to missing nonce verification on the settings form submission and insufficient input sanitization combined with missing output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request granted they can trick an administrator into performing an action such as clicking on a link.

INFO

Published Date :

March 21, 2026, 12:16 a.m.

Last Modified :

March 21, 2026, 12:16 a.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-3572 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update iTracker360 plugin to a version later than 2.2.0 to fix CSRF and XSS vulnerabilities.
  • Update the iTracker360 plugin to the latest version.
  • Ensure nonce verification is implemented on forms.
  • Sanitize all user inputs effectively.
  • Escape all user-supplied output properly.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-3572 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-3572 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-3572 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-3572 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Mar. 21, 2026

    Action Type Old Value New Value
    Added Description The iTracker360 plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in all versions up to and including 2.2.0. This is due to missing nonce verification on the settings form submission and insufficient input sanitization combined with missing output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    Added CWE CWE-79
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.php#L115
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.php#L116
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.php#L187
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L115
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L116
    Added Reference https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L187
    Added Reference https://www.wordfence.com/threat-intel/vulnerabilities/id/5ef842ad-3d23-4206-af3b-b3f55486766f?source=cve
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.