# CVE-2025-14557: XSS in Drupal 7 Facebook Pixel Module

> Stored XSS in the Drupal Facebook Pixel module allows attackers to inject malicious scripts, potentially compromising user sessions and data.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 14 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** CLSA-2026-1789632490, GHSA-gr4q-4g75-6r32

## What is CVE-2025-14557?

CVE-2025-14557 is a medium-severity cross-site scripting vulnerability in Drupal Facebook Pixel, published on 14 Jan 2026. 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 (XSS or 'Cross-site Scripting') vulnerability in Drupal Facebook Pixel facebook_pixel allows Stored XSS.This issue affects Facebook Pixel: from 7.X-1.0 through 7.X-1.1.

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

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

It affects 1 product.


Products: Facebook Pixel Project Facebook Pixel.

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

Apply the vendor's patch.

## Is CVE-2025-14557 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14557 is a medium-severity cross-site scripting vulnerability in Drupal Facebook Pixel, published on 14 Jan 2026. 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-14557 in the wild and no public exploit code.

Affected product: Drupal Facebook Pixel. 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-14557/ (Markdown: https://insights.sbomify.com/CVE-2025-14557/index.md)
```

## Sources

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

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