Tracking ID modification via missing nonce validation
Published Jun 30, 2026 · Updated Jun 30, 2026
Cross-site request forgery in Plugin for Google Analytics by IO technologies 1.1 and earlier allows remote attackers to alter its tracking ID. The ga.php settings handler accepts the ga_id request parameter and writes it to the io-ga-id WordPress option without validating a nonce. Exploitation requires an authenticated site administrator to submit the forged request, such as by clicking an attacker-controlled link, and changes only the stored analytics identifier.
Summary
What happened
Cross-site request forgery in Plugin for Google Analytics by IO technologies 1.1 and earlier allows remote attackers to alter its tracking ID. The ga.php settings handler accepts the ga_id request parameter and writes it to the io-ga-id WordPress option without validating a nonce. Exploitation requires an authenticated site administrator to submit the forged request, such as by clicking an attacker-controlled link, and changes only the stored analytics identifier.
The record
- CVE
- CVE-2026-8944
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- IO Technologies
- Product
- Plugin for Google Analytics by IO technologies
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo