Plugin security / Independent Analytics Pro
Independent Analytics Pro vulnerability: is your WooCommerce store affected?
Independent Analytics Pro has one serious security hole rated 7 or higher out of 10 that someone can use with no login or with only a customer account. The newest was published on 30 October 2026. Every one is fixed: update to 2.16.0 or newer.
Short answer: your store is affected if it runs Independent Analytics Pro older than 2.16.0. Update to 2.16.0 or newer, on a copy of the store first if you can.
The security holes
Newest first. Each one is published in a public security database and fixed in the version shown.
Cross-site scripting
Someone could plant a script that runs in your visitors' or your admins' browsers.
Score 7.2 (high)no login neededAffected: older than 2.16.0Fixed in 2.16.0Published 30 October 2026CVE-2026-104744
Advisory: The Independent Analytics Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'utm_campaign' parameter in all versions up to, and including, 2.15.5 due to insufficient input sanitization and...
How to check your version
- Log in to WordPress and open
Plugins > Installed Plugins. - Find Independent Analytics Pro. The version number is under its name. If it is lower than 2.16.0, your store is affected.
- No login to hand? Open
https://yourstore.com/wp-content/plugins/independent-analytics-pro/readme.txtin a browser, with your own address in place of yourstore.com, and read theStable tagline. Some hosts block this file; then use step 1.
How to fix it
- Make a backup, or better, a staging copy of the store (most hosts have a one-click staging button).
- On the copy, update Independent Analytics Pro to 2.16.0 or newer:
Dashboard > Updates, orUpdate nowon the Plugins page. - If no update shows, it may be a paid version whose licence has run out: download the new version from the seller's site and upload it.
- Place a test order on the copy: add to cart, check out, pay with a test method. Check the pages that use Independent Analytics Pro.
- If everything works, make the same update on the live store and place one more test order.
- If you no longer use Independent Analytics Pro, delete it instead of leaving it deactivated.
Not sure, or no time?
Get a free check of your store: we look at its public pages for plugins with known holes, and reply within one working day. Or we fix it for you: we update your store on a copy, place a test order, and only then change the live store, for a fixed £99 / $119.
Free store check Fix it for me on a copyQuestions
- Which Independent Analytics Pro version fixes it?
- Version 2.16.0 or newer fixes the issue on this page.
- How do I know if my store is affected?
- Your store is affected if it runs Independent Analytics Pro older than 2.16.0. In WordPress, open Plugins and read the version under Independent Analytics Pro. Without logging in, open yourstore.com/wp-content/plugins/independent-analytics-pro/readme.txt and read the Stable tag line.
- I don't use Independent Analytics Pro any more. Is a deactivated copy safe?
- Deactivating it lowers the risk but leaves the old code on your server. If you don't use it, delete it; if you do, update it.
- Can someone fix it for me?
- Yes. We update the store on a copy first, place a test order, and only then make the same change on the live store, for a fixed price.
Vulnerability data: WPVulnerability (wpvulnerability.net, CC0), which links each entry to its CVE or advisory. Store numbers: Tadrik's own checks of public pages, aggregates only. Page updated 5 November 2026.