Google AnalyticatorWordPress extension · Sumo
CVE-2009-5158
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 · uneditedThe google-analyticator plugin before 5.2.1 for WordPress has insufficient HTML sanitization for Google Analytics API text.
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 confidenceThe google-analyticator WordPress plugin before version 5.2.1 contains a Cross-Site Scripting (XSS) vulnerability due to insufficient HTML sanitization of Google Analytics API text input. This allows attackers to inject malicious HTML or script code that executes in the context of other users' browsers.
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 AnalyticatorWordPress extension
< 5.2.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check if google-analyticator plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'google-analyticator' or 'Sumo Google Analyticator' in the list of active or installed plugins.Affected if The plugin appears in the WordPress plugins list, regardless of activation status.
-
Identify the installed version of the pluginIn WordPress admin, go to Plugins > Installed Plugins. Click on the plugin name to view its details, or check the plugin header in the main plugin file (usually in wp-content/plugins/google-analyticator/google-analyticator.php) for the 'Version' comment.Affected if The version number displayed is less than 5.2.1 (for example, 5.2.0, 5.1.9, or any version below 5.2.1).
-
Verify Google Analytics API settings are accessibleIn WordPress admin, navigate to the plugin settings for google-analyticator. Look for fields related to Google Analytics API configuration, typically found under Settings > Google Analyticator or a dedicated settings page provided by the plugin.Affected if The plugin settings page loads and displays input fields for Google Analytics API text input or configuration values.
-
Confirm the vulnerability conditionNo direct exploitation check is provided. The vulnerability exists when the plugin is installed with a version below 5.2.1 and the Google Analytics API input field accepts user-supplied text without proper sanitization.Affected if The plugin version is below 5.2.1 AND the Google Analytics API text input field is present in the plugin settings.
You are affected if the google-analyticator or Sumo Google Analyticator WordPress plugin is installed with any version lower than 5.2.1.
Generated from the published advisory. Verify against your own configuration.
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 data5.2.1
Update the google-analyticator plugin to version 5.2.1 or later which includes proper HTML sanitization. If the plugin is no longer maintained, consider removing it and using an alternative analytics integration method.
Fix this in Google Analyticator
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-5158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-5158 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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