dbcve.org
SelectzeroApplication

CVE-2025-52217

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 2025.5.2 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SelectZero Data Observability Platform versions before 2025.5.2 contain an HTML Injection vulnerability in the Legacy UI. User-supplied input in certain UI fields is not properly sanitized or encoded, allowing attackers to inject arbitrary HTML code that gets rendered in the browser.

MitigationUpgrade to version 2025.5.2 or later. Additionally, implement context-aware output encoding for all user-supplied input rendered in HTML contexts in the Legacy UI to prevent injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SelectzeroApplication
Affected:< 2025.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine SelectZero platform version
    Check the installed version of SelectZero Data Observability Platform using your system's package manager, application metadata, or administrative console. Look for version information in the product's about page, installation directory, or version command output.
    Affected if The installed version is any release before 2025.5.2 (e.g., 2025.5.1, 2025.4.0, earlier releases).
  2. Verify Legacy UI is accessible
    Access the Legacy UI component of SelectZero. This is typically accessible via a specific URL path (such as /legacy, /old-ui, or similar), through a UI toggle, or by logging into an older interface variant. Check administrative settings or documentation for Legacy UI access paths.
    Affected if The Legacy UI is enabled and accessible to users or administrators in the environment.
  3. Identify user input fields in Legacy UI
    Navigate through the Legacy UI and locate input fields where users can submit data. The CVE mentions HTML injection is possible in certain UI fields - examine form inputs, search fields, name/description fields, and any text-entry areas.
    Affected if User input fields exist in the Legacy UI where arbitrary text can be entered and subsequently rendered back in HTML context.
  4. Confirm lack of output encoding
    Submit a benign HTML test payload (such as <b>test</b> or <i>test</i>) in Legacy UI input fields and observe whether the raw HTML tags render as bold/italic text or are displayed as plain text. If the HTML is rendered, output encoding is not properly applied.
    Affected if The injected HTML tags are rendered as formatted text rather than being escaped or displayed as plain text.

You are affected if your SelectZero installation is version 2025.5.1 or earlier AND the Legacy UI is enabled and accessible, allowing user-supplied input to be rendered as unescaped HTML.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.5.2 or later
Fixed in 2025.5.2
Interim mitigation

Upgrade to version 2025.5.2 or later. Additionally, implement context-aware output encoding for all user-supplied input rendered in HTML contexts in the Legacy UI to prevent injection.

Recommended fix High confidence

2025.5.2

  1. 1. Back up your current SelectZero installation including all configuration files and databases
  2. 2. Review the SelectZero 2025.5.2 release notes for any migration requirements or pre-upgrade tasks
  3. 3. Upgrade SelectZero to version 2025.5.2 or later following your existing deployment method (e.g., package manager, container, or manual installation)
  4. 4. After upgrade, clear any browser cache and session data to ensure the new UI components are loaded
  5. 5. Verify the upgrade was successful by checking the version number in the platform's about or settings section
  6. 6. Test that the legacy UI fields properly sanitize HTML input by attempting to inject benign HTML tags in input fields

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Selectzero Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52217 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data