CVE-2025-48920

7.3 HIGH

📋 TL;DR

This CVE describes a cross-site scripting (XSS) vulnerability in the Drupal etracker module that allows attackers to inject malicious scripts into web pages. The vulnerability affects all versions of the etracker module before 3.1.0. Attackers can exploit this to steal user credentials, hijack sessions, or perform actions on behalf of authenticated users.

💻 Affected Systems

Products:
  • Drupal etracker module
Versions: All versions before 3.1.0
Operating Systems: All operating systems running Drupal
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the etracker module's web page generation where user input is not properly sanitized before being included in output.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, take over the Drupal site, install backdoors, exfiltrate sensitive data, or use the compromised site to attack visitors.

🟠

Likely Case

Attackers will typically use this to steal user session cookies and credentials, perform account takeovers, or redirect users to malicious sites.

🟢

If Mitigated

With proper input validation and output encoding, the risk is limited to potential data leakage from the specific vulnerable component.

🌐 Internet-Facing: HIGH - This affects web applications directly exposed to the internet, making them accessible to any attacker.
🏢 Internal Only: MEDIUM - Internal applications are still vulnerable to insider threats or compromised internal systems.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities are commonly exploited and require minimal technical skill. The advisory provides enough detail for attackers to craft exploits.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.1.0

Vendor Advisory: https://www.drupal.org/sa-contrib-2025-074

Restart Required: No

Instructions:

1. Log into your Drupal admin panel. 2. Navigate to Extend > Update. 3. Check for available updates. 4. Update etracker module to version 3.1.0 or later. 5. Clear all caches from Configuration > Development > Performance.

🔧 Temporary Workarounds

Disable etracker module

all

Temporarily disable the vulnerable module until patching is possible

drush pm-disable etracker

Implement Content Security Policy

all

Add CSP headers to mitigate XSS impact by restricting script execution

Add 'Content-Security-Policy' header to web server configuration

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Enable Drupal's built-in XSS protection features and ensure all user input is properly sanitized

🔍 How to Verify

Check if Vulnerable:

Check the etracker module version in Drupal admin at Extend > Installed modules or use: drush pm-list | grep etracker

Check Version:

drush pm-list --fields=name,version | grep etracker

Verify Fix Applied:

Confirm etracker module version is 3.1.0 or higher and test the previously vulnerable functionality

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript payloads in request logs
  • Multiple requests with script tags or encoded payloads
  • Requests to etracker endpoints with suspicious parameters

Network Indicators:

  • HTTP requests containing script tags, javascript: URIs, or encoded HTML entities
  • Unusual outbound connections from the Drupal server following etracker requests

SIEM Query:

source="web_server_logs" AND (uri="*etracker*" OR user_agent="*etracker*") AND (request="*<script>*" OR request="*javascript:*" OR request="*%3Cscript%3E*")

🔗 References

📤 Share & Export