Security readout for executives and security teams
Plain-English summary
ExactMetrics versions through 9.1.2 may let any logged-in WordPress subscriber obtain a connected Google Ads access token or reset integration settings. Token exposure could compromise advertising data or connected-account access, depending on the token’s permissions. The supplied evidence does not show unauthenticated access or confirmed exploitation.
Executive priority
Prioritize remediation for sites with active Google Ads connections or broadly issued subscriber accounts. Treat suspected token access as a credential-exposure incident and rotate the token promptly. Other affected sites should enter the normal expedited patch cycle once a vendor-confirmed fixed release is identified.
Technical view
Two ExactMetrics AJAX handlers, get_ads_access_token() and reset_experience(), reportedly validate a broadly available admin nonce but omit capability checks. Subscribers can access an admin page where that nonce is localized. This creates CWE-862 exposure for token disclosure and settings modification. The supplied CVSS vector says PR:N, but the vulnerability description explicitly requires an authenticated Subscriber-level account.
Likely exposure
WordPress sites running ExactMetrics 9.1.2 or earlier are potentially affected, particularly when Google Ads integration is configured and untrusted subscriber accounts exist. The bundle’s structured affected-version entry is inconsistent, listing version "0" and default unaffected; therefore, confirm applicability against vendor or Wordfence guidance.
Exploitation context
The issue is reportedly reachable remotely by a logged-in Subscriber or higher role and requires no special capability beyond obtaining the exposed nonce. The bundle marks KEV false and provides no evidence of active exploitation. Public references include affected code and a changeset, but the bundle does not establish exploit prevalence.
Researcher notes
The core defect is authorization, not nonce validation: a nonce demonstrates request context but does not establish permission. Evidence supports Subscriber+ access despite the supplied CVSS vector indicating PR:N. The source bundle does not name a fixed version, and its structured affected-version data conflicts with the narrative range, reducing certainty around remediation boundaries.
Mitigation direction
- Check ExactMetrics and vendor guidance for a release confirmed to fix CVE-2026-5488.
- Update to the confirmed fixed release when identified, following normal backup and testing procedures.
- Revoke and replace connected Google Ads tokens if exposure is suspected.
- Temporarily disable the plugin or Google Ads integration where immediate token protection is required.
- Review and remove unnecessary or untrusted WordPress subscriber accounts.
Validation and detection
- Inventory ExactMetrics installations and record their exact versions.
- Identify affected sites using ExactMetrics 9.1.2 or earlier.
- Determine whether Google Ads integration is configured on each affected site.
- Review WordPress and web logs for unexpected exactmetrics_ads_get_token activity.
- Confirm the remediated handlers enforce an appropriate capability check, not only nonce validation.
- Verify old Google Ads tokens are invalid after rotation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-5488 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4WordfenceVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6a4359e4-5843-4d2c-b288-5c35f819241a?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/google-analytics-dashboard-for-wp/trunk/includes/ppc/google/class-exactmetrics-google-ads.php#L243CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/google-analytics-dashboard-for-wp/tags/9.0.3/includes/ppc/google/class-exactmetrics-google-ads.php#L243CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/google-analytics-dashboard-for-wp/trunk/includes/admin/admin-assets.php#L196CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/google-analytics-dashboard-for-wp/tags/9.0.3/includes/admin/admin-assets.php#L196CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3513041%40google-analytics-dashboard-for-wp&new=3513041%40google-analytics-dashboard-for-wp&sfp_email=&sfph_mail=CVE reference, Wordfence
- https://research.cleantalk.org/cve-2026-5488CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.