# CVE-2025-4415: Piwik PRO - Moderately critical - Cross Site Scripting - SA-CONTRIB-2025-058

> An attacker can inject malicious scripts into web pages viewed by other users via the Piwik PRO Drupal module.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** DRUPAL-CONTRIB-2025-058, GHSA-fhm3-85qw-2fgx

## What is CVE-2025-4415?

CVE-2025-4415 is a medium-severity cross-site scripting vulnerability in Drupal Piwik PRO, published on 21 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Piwik PRO allows Cross-Site Scripting (XSS).This issue affects Piwik PRO: from 0.0.0 before 1.3.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-4415?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/piwik_pro` | Packagist:https://packages.drupal.org/8 | All versions | 1.3.2 |

Products: Matomo Piwik Pro.

## How do I fix CVE-2025-4415?

Upgrade to a fixed version.

## Is CVE-2025-4415 being exploited?

There is no known exploitation of CVE-2025-4415 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4415 and fix it if it is affected.

What it is: CVE-2025-4415 is a medium-severity cross-site scripting vulnerability in Drupal Piwik PRO, published on 21 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-4415 in the wild and no public exploit code.

Affected product: Drupal Piwik PRO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4415/ (Markdown: https://insights.sbomify.com/CVE-2025-4415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4415
- OSV: https://osv.dev/vulnerability/CVE-2025-4415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4415/
Summaries are generated and may contain mistakes; the official description above is the record.