dbcve.org
Mainwp Google Analytics ExtensionWordPress extension · Mainwp

CVE-2023-23651

HIGH · 8.8 CVSS v3.1 Published 2023-10-12
Fix available
A fix is available. Upgrade to after 4.0.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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. (subscriber+) SQL Injection (SQLi) vulnerability in MainWP Google Analytics Extension plugin <= 4.0.4 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 · high confidence

Authenticated SQL Injection vulnerability in MainWP Google Analytics Extension plugin versions 4.0.4 and below allows subscriber+ level users to inject malicious SQL queries via unsanitized input parameters.

MitigationUpdate MainWP Google Analytics Extension to version 4.0.5 or later. Until patched, restrict user permissions to below subscriber level and monitor for suspicious database activity.

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
Mainwp Google Analytics ExtensionWordPress extension
Affected:<= 4.0.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Google Analytics Extension is installed
    Navigate to MainWP > Extensions and verify that the Google Analytics Extension is listed as installed and active
    Affected if The extension is installed and active in the MainWP dashboard
  2. Identify installed extension version
    In the Extensions list, locate the version number displayed for the Google Analytics Extension
    Affected if The version listed is 4.0.4 or lower
  3. Check for subscriber-level or higher user accounts
    Navigate to WordPress Users menu and review all user accounts, noting their role levels
    Affected if Any user account with Subscriber, Editor, Author, or Administrator role exists in the system
  4. Verify SQL query logging is enabled
    Check WordPress debug logs or database query logs for suspicious or unexpected SQL queries, particularly those containing UNION SELECT or similar SQL injection patterns
    Affected if Unsanitized SQL queries appear in logs originating from the Google Analytics Extension

A user is affected if the MainWP Google Analytics Extension version 4.0.4 or lower is installed and active alongside at least one subscriber-level or higher user account.

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
Upgrade available Upgrade to a release after 4.0.4
Interim mitigation

Update MainWP Google Analytics Extension to version 4.0.5 or later. Until patched, restrict user permissions to below subscriber level and monitor for suspicious database activity.

Fix this in Mainwp Google Analytics Extension Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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