Tag-container state changes via unprotected routes
Published Mar 31, 2025 · Updated Apr 29, 2025
CSRF in Drupal Google Tag before 1.8.0 and 2.0.0 through 2.0.7 allows remote attackers to enable or disable tag containers. The module's container enable and disable routes accept state-changing requests without CSRF protection. Exploitation requires user interaction and knowledge of the container's random machine name, and changes only that container's enabled state.
Summary
What happened
CSRF in Drupal Google Tag before 1.8.0 and 2.0.0 through 2.0.7 allows remote attackers to enable or disable tag containers. The module's container enable and disable routes accept state-changing requests without CSRF protection. Exploitation requires user interaction and knowledge of the container's random machine name, and changes only that container's enabled state.
The record
- CVE
- CVE-2025-31683
- Published
- Mar 31, 2025
- Updated
- Apr 29, 2025
- Vendor
- OAuth.js
- Product
- Google Tag
- Classifications
- CWE-352, CAPEC-62, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Apr 29, 2025Record 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.0.0 <1.8.0
- Affected versionversion=2.0.0 <2.0.8
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