Analytics disablement via missing nonce validation
Published Aug 26, 2024 · Updated Apr 28, 2026
CSRF in Analytify 5.3.1 and earlier allows remote attackers to disable Google Analytics tracking through a forged opt-out request. The optout_yes() function accepts the state-changing request without valid nonce verification and records the tracking opt-out. Exploitation requires a logged-in site administrator to visit a crafted page or link; the reported effect is limited to disabling analytics tracking.
Summary
What happened
CSRF in Analytify 5.3.1 and earlier allows remote attackers to disable Google Analytics tracking through a forged opt-out request. The optout_yes() function accepts the state-changing request without valid nonce verification and records the tracking opt-out. Exploitation requires a logged-in site administrator to visit a crafted page or link; the reported effect is limited to disabling analytics tracking.
The record
- CVE
- CVE-2024-43265
- Published
- Aug 26, 2024
- Updated
- Apr 28, 2026
- Vendor
- Analytify
- Product
- Analytify
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=n/a <=5.3.1 changes=[{"at":"5.4.0","status":"unaffected"}]
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