Skip to main content
WordPress plugin recordReviewed

MonsterInsights vulnerability records, and who can see its reports or change its Google connection

MonsterInsights loads a Google Analytics tag in the site header and shows reports inside WordPress to the roles its settings allow.

Read its records by version field, then check the connection, the tag and each role list without changing anything.

MonsterInsights vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 12 records for MonsterInsights. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 11.1.0

Worked out from data retrieved on .

Every affected range listed in this source for MonsterInsights ends before version 11.1.0.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. MonsterInsights <= 11.0.0 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 11.0.0

    Patched versions: 11.1.0

    Update to at least version 11.1.0.

  2. MonsterInsights <= 10.1.2 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure And Plugin Integration Reset

    Published:
    Last updated:
    Severity:
    High (CVSS 7.1)
    Affected versions
    • All versions up to and including 10.1.2

    Patched versions: 10.1.3

    Update to at least version 10.1.3.

  3. Google Analytics by Monster Insights <= 8.21.0 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 8.21.0

    Patched versions: 8.22.0

    Update to at least version 8.22.0.

  4. Google Analytics by Monster Insights <= 8.14.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 8.14.0

    Patched versions: 8.14.1

    Update to at least version 8.14.1.

  5. MonsterInsights <= 8.12.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 8.12.0

    Patched versions: 8.12.1

    Update to at least version 8.12.1.

Show 7 older records
  1. MonsterInsights <= 8.9.0 - Unauthenticated Stored Cross-Site Scripting via Google Analytics

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 8.9.0

    Patched versions: 8.9.1

    Update to at least version 8.9.1.

  2. MonsterInsights - Google Analytics Dashboard for WordPress <= 7.1 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 7.1

    Patched versions: 7.2.0

    Update to at least version 7.2.0.

  3. MonsterInsights - Google Analytics Dashboard for WordPress <= 5.4.4 - Authenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.8)
    Affected versions
    • All versions up to and including 5.4.4

    Patched versions: 5.4.5

    Update to at least version 5.4.5.

  4. MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy) <= 5.3.3 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 5.3.3

    Patched versions: 5.4

    Update to at least version 5.4.

  5. MonsterInsights - Google Analytics Dashboard for WordPress <= 5.3.2 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 5.3.2

    Patched versions: 5.3.3

    Update to at least version 5.3.3.

  6. MonsterInsights - Google Analytics Dashboard for WordPress <= 5.3.2 - Authenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 5.3.2

    Patched versions: 5.3.3

    Update to at least version 5.3.3.

  7. MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy) <= 5.1.2 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.5)
    Affected versions
    • All versions up to and including 5.1.2

    Patched versions: 5.1.3

    Update to at least version 5.1.3.

Check MonsterInsights on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

What MonsterInsights connects, collects and shows

The WordPress.org listing says MonsterInsights connects a WordPress site with Google Analytics and shows reports right inside the WordPress dashboard.

It calls this plugin "the lite version of MonsterInsights Pro plugin", and its installation steps say "Navigate to the Insights tab in your WordPress admin menu and configure the plugin."

Its own settings take input: the Google connection, or a GA4 Measurement ID entered on its own, which the plugin warns means "you won't be able to use any of the reporting and some of the tracking features"; its role lists; and summary emails. The listing's reports include an Audience Report on visitors' country, interests, device, age and gender, among other things, and the changelog places Page Insights in the editor sidebar, the admin bar panel and the classic editor metabox, beside a dashboard widget and a Site Insights block for sharing website stats with visitors.

Its role settings carry the labels "Allow These User Roles to See Reports", "Allow These User Roles to Save Settings" and "Exclude These User Roles From Tracking". Two passages of its help text open "A user with the 'manage_options' capability and any user with at least one of these roles", one ending "can view the reports" and the other "will have permission to view and save the settings panel".

Reading the MonsterInsights titles and version fields

The records in the history on this page are the ones the source data files under the slug google-analytics-for-wordpress, though their titles name the plugin in more than one way: some begin "MonsterInsights", others "Google Analytics by Monster Insights" or "MonsterInsights - Google Analytics Dashboard for WordPress". Treat the name as a label and match on the affected range and patched versions field.

Cross-site scripting runs through the history from its earliest titles. CVE-2022-3904 has a title ending "Unauthenticated Stored Cross-Site Scripting via Google Analytics", with all versions up to and including 8.9.0 affected and 8.9.1 in its patched versions field. CVE-2023-23999 has a title ending "Authenticated (Contributor+) Stored Cross-Site Scripting" and covers all versions up to and including 8.14.0, with 8.14.1 in its patched versions field.

The words "Missing Authorization" recur in the titles as well. CVE-2026-5371 has a title ending "Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure And Plugin Integration Reset"; its affected range is all versions up to and including 10.1.2, and its patched versions field lists 10.1.3. CVE-2026-11366's title ends "Missing Authorization"; it covers all versions up to and including 11.0.0, and its patched versions field lists 11.1.0.

Read those two together: version 10.1.3, which the patched versions field of CVE-2026-5371 lists, sits inside the affected range of CVE-2026-11366. That record's range ends at 11.0.0 and its patched versions field lists 11.1.0; the fields say nothing about the versions between the two, so for that record the patched version is the one to reach.

Some records carry no CVE id. Two from March 2015, with titles ending "Stored Cross-Site Scripting" and "Authenticated Stored Cross-Site Scripting", share the same fields: all versions up to and including 5.3.2 affected, 5.3.3 patched. An installed version in that range sits inside both.

Before relying on the update guidance at the top of the history, also read the changelog on the plugin's WordPress.org listing, where one entry describes "Security hardening across admin and reporting requests" and another "Security hardening for license actions and credential handling".

Checking a MonsterInsights site without changing it

Among the plugin's own labels are "Reconnect MonsterInsights", "Verify Credentials", "Force Deauthenticate" and "Disconnect MonsterInsights".

On a site you are authorised to review, press none of them: the checks here only read and record.

Plugin version and edition

The Description column on the Plugins screen includes each plugin's version number; record every MonsterInsights entry with its version and the date. If the plugin shows "A valid license has been added to MonsterInsights but you are still using the Lite version.", copy it.

Then record the Automatic update column and which of the plugin's update messages appears, among them "MonsterInsights automatic updates are enabled", "MonsterInsights minor updates are enabled", which it says brings "bugfixes and security updates, but not major features", and "Automatic updates are disabled".

Google connection

Find where the plugin shows "Google Authentication" and record which connection the site uses, a Google connection or a GA4 Measurement ID on its own, and what it shows as the "Active Profile". Copy any connection message word for word, such as "Your site is connected to MonsterInsights!" or "This connection is missing its Google credentials, so reports will not load." Record whichever of the plugin's status messages appears: "Your website is authenticated with MonsterInsights", "You are using Manual GA4 Measurement ID output" or "Please configure your Google Analytics settings".

Tracking output in the page source

The listing's FAQ says that by default no data goes to Google Analytics for logged-in WordPress administrators and editors, and that "MonsterInsights loads code in WordPress header". Open the home page and one inner page in a private window, signed out. View the source, look for the Google Analytics code in the head, and write down each Measurement ID it carries and any second Google tag.

Compare the ID with the connection you recorded, then record the roles in "Exclude These User Roles From Tracking".

Report permissions

Record every role ticked in "Allow These User Roles to See Reports" and, from the Role column and role filter links on the Users screen, who holds each. Add every user with the manage_options capability, which the help text on viewing reports also names.

Then record where reports surface: which of "Enabled", "Dashboard Widget Only" and "Disabled" is chosen for reports and the dashboard widget; whether "Hide Admin Bar Reports" is on; whether "Enable Email Summaries", which an October 2023 changelog entry places under Settings -> Advanced, is on, with the email addresses configured; and any public page showing a Site Insights block. Leave the button that sends an example summary alone.

Administration access

Record the roles in "Allow These User Roles to Save Settings" and list the users in each. List every Administrator too: WordPress's Roles and Capabilities page gives an Administrator access to all administration features within a single site. The plugin's messages to a user without permission to authenticate, re-authenticate or deauthenticate each say to check "that your role is included in the MonsterInsights permissions settings".

What a MonsterInsights version match leaves open

Matching the installed version against the affected ranges shows whether the site sits inside a known MonsterInsights record.

It cannot show whether anyone used the flaw, which roles the reports and settings lists hold, whether a second Google tag loads, or who receives the summary emails.

CVE-2026-5371's title includes "Authenticated (Subscriber+)", and a version number cannot say what a subscriber reaches on this site. A WordPress security audit signs in as each role with test accounts, captures requests an administrator makes in plugin settings screens and replays them as a subscriber, then records what happened.

Frequently asked questions

The source data files these records under google-analytics-for-wordpress, the slug of the plugin the listing calls "the lite version of MonsterInsights Pro plugin". Being filed there does not show whether a record also applies to Pro. The plugin's own text includes a request to uninstall the MonsterInsights Lite Plugin, saying "Your Pro version of MonsterInsights may not work as expected until the Lite version is uninstalled." Record which edition the Plugins screen lists.

If you are signed in as an administrator or editor, that may be the default. The listing's FAQ says "By default we do not send data to Google Analytics for logged-in WordPress administrators and editors", and that more roles can be blocked. Check the tag signed out, in a private window, and read the roles in "Exclude These User Roles From Tracking".

The listing's FAQ answers no: "You should only use one Google Analytics plugin on your WordPress site", and it recommends uninstalling others before installing MonsterInsights. The plugin's own notice reads "We have detected multiple tracking codes! You should remove non-MonsterInsights ones." A second Google tag in the page source is the thing to write down.

The plugin's own text for a disconnected site reads "You've disconnected your site from MonsterInsights. Your site is no longer being tracked by Google Analytics and you won't see reports anymore." So the connection check on this page reads and presses nothing. A connection the plugin reports as missing its Google credentials is for the site owner to fix, not something to reset during a review.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 7 of the 12 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.