CVE-2026-3572 iTracker360 <= 2.2.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'itracker_license' Settings Field
Unauthenticated attackers can inject arbitrary scripts via CSRF in the iTracker360 plugin, potentially compromising administrator accounts.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-3572?
CVE-2026-3572 is a medium-severity cross-site scripting vulnerability in iTracker360, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-3572?
How do I fix CVE-2026-3572?
No fix has been published for CVE-2026-3572 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-3572 being exploited?
There is no known exploitation of CVE-2026-3572 in the wild and no public exploit code.
Sources
Also known as GHSA-7rfx-3hr4-gv82.