dbcve.org
Google Analytics DashboardWordPress extension · Monsterinsights

CVE-2023-23999

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-18
Fix available
A fix is available. Upgrade to 8.14.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in MonsterInsights plugin <= 8.14.0 versions.

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 · moderate confidence

Authenticated (contributor+) stored Cross-Site Scripting (XSS) vulnerability in MonsterInsights WordPress plugin versions 8.14.0 and below allows users with contributor-level or higher privileges to inject malicious JavaScript that persists and executes when other users view the affected content.

MitigationUpdate MonsterInsights plugin to version 8.14.1 or later, as the vendor has released a patch addressing this stored XSS vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Google Analytics DashboardWordPress extension
Affected:< 8.14.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 MonsterInsights plugin is installed
    Navigate to WordPress admin > Plugins and look for 'MonsterInsights Google Analytics Dashboard' in the installed plugins list, or check the file system at /wp-content/plugins/monsterinsights/ for the main plugin file.
    Affected if MonsterInsights is not found in the plugins list or directory.
  2. Check installed MonsterInsights version
    In WordPress admin, go to Plugins > Installed Plugins > MonsterInsights and read the version number from the plugin description. Alternatively, check the plugin header in /wp-content/plugins/monsterinsights/monsterinsights.php for 'Version:' value.
    Affected if The version displayed is 8.14.0 or lower.
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that MonsterInsights shows as 'Active' (not deactivated or deleted).
    Affected if MonsterInsights is installed but not active.
  4. Verify contributor-level or higher user roles exist
    In WordPress admin, go to Users > Users List and check if any users exist with the role of 'Contributor', 'Author', 'Editor', or 'Administrator'. Alternatively, check in Users > User Roles.
    Affected if At least one user account with contributor-level or higher privileges exists in WordPress.

You are affected if MonsterInsights Google Analytics Dashboard plugin is installed, active, running version 8.14.0 or below, and your WordPress site has at least one user with contributor-level or higher privileges.

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.

dbcve · scoped
Upgrade available Upgrade to 8.14.1 or later
Fixed in 8.14.1
Interim mitigation

Update MonsterInsights plugin to version 8.14.1 or later, as the vendor has released a patch addressing this stored XSS vulnerability.

Recommended fix High confidence

MonsterInsights version 8.14.1 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the MonsterInsights (Google Analytics Dashboard) plugin
  4. Check if the current version is 8.14.0 or lower
  5. If vulnerable, click 'Update Now' to upgrade to version 8.14.1 or later
  6. Verify the update was successful by checking the plugin version after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Google Analytics Dashboard Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23999 — 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-2023-23999 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