Drupal Plausible tracking is vulnerable to XSSGHSA-pr6m-qwrr-mrw9
MEDIUMGHSA-pr6m-qwrr-mrw9 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in drupal/plausible_tracking. A fix is available for drupal/plausible_tracking — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-pr6m-qwrr-mrw9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
drupal/plausible_trackingReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Plausible tracking allows Cross-Site Scripting (XSS). This issue affects Plausible tracking: from 0.0.0 before 1.0.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/plausible_tracking | all versions | 1.0.2composer require drupal/plausible_tracking:^1.0.2 |
Affected Products
plausible trackingplausible_tracking_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/plausible_tracking, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/plausible_tracking to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr6m-qwrr-mrw9 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-pr6m-qwrr-mrw9 in your dependencies?
Find it across Packagist, including transitive dependencies.