Stored XSS via unsanitized container ID
Published Aug 15, 2025 · Updated Aug 15, 2025
Stored XSS in Drupal GoogleTag Manager before 1.10.0 allows remote authenticated users to execute script in site visitors' browsers. The GTM-ID configuration field insufficiently sanitizes input and inserts the saved value directly into a script tag. The attacker needs the Administer gtm permission, and the 20-character field limit constrains the payload while permitting browser-side code execution.
Summary
What happened
Stored XSS in Drupal GoogleTag Manager before 1.10.0 allows remote authenticated users to execute script in site visitors' browsers. The GTM-ID configuration field insufficiently sanitizes input and inserts the saved value directly into a script tag. The attacker needs the Administer gtm permission, and the 20-character field limit constrains the payload while permitting browser-side code execution.
The record
- CVE
- CVE-2025-8362
- Published
- Aug 15, 2025
- Updated
- Aug 15, 2025
- Vendor
- OAuth.js
- Product
- GoogleTag Manager
- Classifications
- CWE-79, CAPEC-63, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 15, 2025CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.10.0
What conditions does exploitation require?
What is affected?
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