# CVE-2025-50891: Cross-site scripting in server-side backend for Site Tracking

> Attackers can inject HTML or execute arbitrary code via cookie hijacking in the Adform Site Tracking server-side backend.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-87jv-7r2h-c6wf

## What is CVE-2025-50891?

CVE-2025-50891 is a high-severity cross-site scripting vulnerability in Adform server-side backend for Site Tracking, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server-side backend for Adform Site Tracking before 2025-08-28 allows attackers to inject HTML or execute arbitrary code via cookie hijacking. NOTE: a customer does not need to take any action to update locally installed software (such as Adform Site Tracking 1.1).

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

No fix has been published for CVE-2025-50891 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50891 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50891 is a high-severity cross-site scripting vulnerability in Adform server-side backend for Site Tracking, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50891 in the wild and no public exploit code.

Affected product: Adform server-side backend for Site Tracking. 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-50891/ (Markdown: https://insights.sbomify.com/CVE-2025-50891/index.md)
```

## Sources

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

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