dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3572

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The iTracker360 WordPress plugin is vulnerable to CSRF-privileged Stored XSS in versions up to 2.2.0. The settings form lacks nonce verification, allowing attackers to forge administrative requests. Combined with missing input sanitization and output escaping on the settings parameters, this enables injection of arbitrary JavaScript that executes when administrators view the affected admin pages.

MitigationUpdate to a patched version beyond 2.2.0 that implements nonce verification on all settings form submissions and applies proper input sanitization and output escaping. As an interim measure, administrators should avoid clicking untrusted links.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify iTracker360 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for iTracker360 in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, particularly version 2.2.0 or below.
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find iTracker360, and check the version number displayed below the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/itracker360/itracker360.php for the Version tag.
    Affected if The installed version is 2.2.0 or any version up to 2.2.0.
  3. Inspect settings form for nonce verification
    Access the plugin settings page (typically under Settings > iTracker360 or a dedicated iTracker360 menu). View the page source (right-click > View Page Source) or examine the plugin PHP files in /wp-content/plugins/itracker360/. Look for wp_nonce_field or wp_nonce_verify calls within the settings form handler.
    Affected if No nonce verification is found in the settings form submission handler, meaning CSRF protection is missing.
  4. Check settings parameters for input sanitization
    Examine the plugin PHP files that handle settings form submissions. Look for sanitize_callback functions or explicit sanitization functions like sanitize_text_field, esc_attr, or other WP sanitization functions applied to settings inputs.
    Affected if Settings parameters lack sanitization functions before being saved to the database.
  5. Verify output escaping on settings display
    Examine the plugin PHP files that render the settings page. Look for escaping functions like esc_html, esc_attr, or esc_textarea applied when displaying saved settings values back to the admin page.
    Affected if Saved settings values are output without proper escaping functions, allowing stored XSS execution.

A user is affected if the iTracker360 plugin version is 2.2.0 or below AND the settings form lacks nonce verification AND settings inputs/outputs lack sanitization/escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version beyond 2.2.0 that implements nonce verification on all settings form submissions and applies proper input sanitization and output escaping. As an interim measure, administrators should avoid clicking untrusted links.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3572 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data