CVE-2026-3572 | iTracker360 Plugin up to 2.2.0 on WordPress Setting cross site scripting

VDB-352307 · CVE-2026-3572 · GCVE-0-2026-3572 ITRACKER360 PLUGIN UP TO 2.2.0 ON WORDPRESS SETTING CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 0.81+ Summaryinfo A vulnerability marked as problematic has been reported in iTracker360 Plugin up to 2.2.0 on WordPress. Affected is an unknown function of the component Setting Handler. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2026-3572. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in iTracker360 Plugin up to 2.2.0 on WordPress. This issue affects an unknown code of the component Setting Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is: 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. The weakness was disclosed by Osvaldo Noe Gonzalez Del Rio. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-3572 since 03/04/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK. Upgrading to version 2.1.9 eliminates this vulnerability. Productinfo Type WordPress Plugin Name iTracker360 Plugin Version 2.0 2.1 2.2.0 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.2 VulDB Meta Temp Score: 5.1 VulDB Base Score: 4.3 VulDB Temp Score: 4.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.1 CNA Vector (Wordfence): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross site scripting CWE: CWE-79 / CWE-94 / CWE-74 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: iTracker360 Plugin 2.1.9 Timelineinfo 03/04/2026 CVE reserved 03/21/2026 +17 days Advisory disclosed 03/21/2026 +0 days VulDB entry created 03/21/2026 +0 days VulDB entry last update Sourcesinfo Advisory: wordfence.com Researcher: Osvaldo Noe Gonzalez Del Rio Status: Confirmed CVE: CVE-2026-3572 (🔒) GCVE (CVE): GCVE-0-2026-3572 GCVE (VulDB): GCVE-100-352307 Entryinfo Created: 03/21/2026 08:14 Changes: 03/21/2026 08:14 (66) Complete: 🔍 Cache ID: 99:0D7:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸