# CVE-2025-52217: Cross-site scripting in n/a

> Attackers can inject arbitrary HTML into legacy UI fields, potentially leading to script execution or session hijacking in SelectZero Data Observability Platform.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-q24h-xm83-9vcm

## What is CVE-2025-52217?

CVE-2025-52217 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SelectZero Data Observability Platform before 2025.5.2 is vulnerable to HTML Injection. Legacy UI fields improperly handle user-supplied input, allowing injection of arbitrary HTML.

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

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

It affects 1 product.


Products: Selectzero Selectzero.

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

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

## Is CVE-2025-52217 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-52218](https://insights.sbomify.com/CVE-2025-52218/): Cross-site scripting in n/a (high 7.5)
- [CVE-2025-52219](https://insights.sbomify.com/CVE-2025-52219/): Open redirect in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52217 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-52217 in the wild and no public exploit code.

Affected product: n/a. 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-52217/ (Markdown: https://insights.sbomify.com/CVE-2025-52217/index.md)
```

## Sources

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

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