Google AnalyticatorWordPress extension · Sumo
CVE-2015-4697
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 · uneditedCross-site request forgery (CSRF) vulnerability in Google Analyticator Wordpress Plugin before 6.4.9.3 rev @1183563.
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 confidenceCross-site request forgery (CSRF) vulnerability in Google Analyticator WordPress plugin versions prior to 6.4.9.3 allows remote attackers to trick authenticated administrators into performing unintended actions by leveraging the lack of anti-CSRF token validation in plugin administrative functions.
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
<= 6.4.9.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Analyticator plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Google Analyticator' or 'Sumo Google Analyticator' in the list of active plugins.Affected if The plugin appears in the list of installed plugins, regardless of activation status.
-
Locate the installed plugin versionIn the WordPress Plugins admin page, click on the plugin name to view details, or access the plugin files via FTP/cPanel and open the main plugin PHP file (often named something like google-analyticator.php) to find the version number in the plugin header comment.Affected if A version number is displayed or found in the plugin header.
-
Compare version to affected rangeCompare the installed version you found against the affected range: versions prior to 6.4.9.3. If the installed version is 6.4.9.3 or higher, the vulnerability is patched.Affected if Installed version is less than 6.4.9.3 (for example, 6.4.9.2, 6.4.8, 6.4.7, etc.).
-
Verify anti-CSRF token implementation (optional)Access the plugin source code and inspect administrative function files for WordPress nonces (wp_nonce_field, wp_verify_nonce, or check_admin_referer). Look for these token validations on any state-changing actions such as settings updates, button clicks, or form submissions in the plugin admin pages.Affected if No nonce verification is found in the plugin administrative functions handling user actions.
A user is affected if the Google Analyticator plugin is installed with a version number less than 6.4.9.3 and lacks anti-CSRF token validation in its administrative functions.
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 dataUpdate Google Analyticator to version 6.4.9.3 or later. Review admin session activity and implement WordPress nonces (anti-CSRF tokens) on all state-changing plugin actions.
Fix this in Google Analyticator
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4697 — 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-2015-4697 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