Security readout for executives and security teams
Plain-English summary
CVE-2026-3572 affects the iTracker360 WordPress plugin up to and including version 2.2.0. If an administrator is tricked into clicking a malicious link or taking a similar action, an attacker may store script in plugin settings. That script could run later in a user’s browser within the site context.
Executive priority
Treat as a near-term WordPress hygiene item, not an emergency based on current evidence. Prioritize internet-facing or business-critical WordPress sites where administrators frequently work in active sessions. Remediate or disable affected installations once vendor guidance is confirmed.
Technical view
The issue is CSRF leading to stored XSS through the itracker_license settings field. Sources cite missing nonce verification on settings submission, insufficient input sanitization, and missing output escaping. CVSS 3.1 is 6.1, with network attack vector, no attacker privileges, required user interaction, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to WordPress sites running iTracker360 versions up to and including 2.2.0. Exploitation requires social engineering of an administrator or equivalent user into performing an action. Sites without this plugin are not affected based on the provided sources.
Exploitation context
The source bundle does not indicate known active exploitation, and KEV status is false. The practical risk is phishing or lure-based abuse against administrators, followed by persistent script execution from stored plugin settings.
Researcher notes
Evidence supports a CSRF-to-stored-XSS path in iTracker360 settings handling, specifically the itracker_license field. Public references include Wordfence and WordPress Trac code locations. The bundle does not provide an official fixed version, exploit-in-the-wild evidence, or detailed vendor advisory beyond the listed references.
Mitigation direction
- Inventory WordPress sites for the iTracker360 plugin and record installed versions.
- Prioritize sites running iTracker360 2.2.0 or earlier for review.
- Check Wordfence, WordPress plugin, and vendor guidance for a fixed version or official mitigation.
- Disable or remove the plugin if it is not business-critical and no fix is available.
- Remind administrators not to click unsolicited admin-session links.
Validation and detection
- Confirm whether iTracker360 is installed on each WordPress instance.
- Check the installed plugin version against the affected range: up to and including 2.2.0.
- Review plugin settings for unexpected changes in the license field.
- Inspect administrative audit logs for suspicious settings updates.
- Verify remediation by confirming an official fixed version or removal of the plugin.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3572 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/5ef842ad-3d23-4206-af3b-b3f55486766f?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/itracker360/trunk/itracker360.php#L187CVE reference
- https://plugins.trac.wordpress.org/browser/itracker360/tags/2.1.9/itracker360.php#L187CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.