dbcve.org
SelectzeroApplication

CVE-2025-52218

HIGH · 7.5 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 2025.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 Content Spoofing / Text Injection. Improper sanitization of unspecified parameters allows attackers to inject arbitrary text or limited HTML into the login page.

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 · moderate confidence

SelectZero Data Observability Platform before version 2025.5.2 contains a content spoofing/text injection vulnerability in the login page due to improper sanitization of certain input parameters. Attackers can inject arbitrary text or limited HTML into the login page, potentially enabling phishing attacks or credential theft by displaying deceptive content to users.

MitigationUpgrade to version 2025.5.2 or later. If immediate upgrade is not feasible, implement strict input validation and output encoding for all parameters rendered on the login page to prevent unauthorized content 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify installed SelectZero version
    Locate and retrieve the version number of the SelectZero Data Observability Platform installation using your system's package manager, software inventory, or application metadata. Common methods include checking the installed packages list, examining the application banner, or querying the software directly.
    Affected if The installed version is lower than 2025.5.2 (for example, 2025.5.1, 2025.4.x, or any earlier release).
  2. Confirm login page accessibility
    Verify that the SelectZero web interface login page is accessible and exposed. Determine if external users or internal network clients can reach the login endpoint.
    Affected if The login page is publicly or broadly accessible and the installed version is below 2025.5.2.
  3. Inspect login page for input reflection
    Submit test input through common login page parameters (such as username, email, or redirect parameters) and examine whether the submitted values appear in the rendered page without proper encoding or sanitization.
    Affected if Input submitted to the login page is reflected back in the response without HTML encoding or sanitization, indicating the vulnerability is present.
  4. Review web application logs for injection attempts
    Examine web server logs, application logs, or WAF logs for unusual patterns in login page parameters that may indicate exploitation of this vulnerability.
    Affected if Logs show injection attempts using HTML tags or arbitrary text in login page parameters, confirming active exploitation of the content spoofing flaw.

You are affected if your SelectZero installation is any version prior to 2025.5.2 and the login page is accessible, as this combination allows arbitrary text or HTML injection into the login page.

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. If immediate upgrade is not feasible, implement strict input validation and output encoding for all parameters rendered on the login page to prevent unauthorized content injection.

Recommended fix Moderate confidence

2025.5.2

  1. 1. Identify the current version of SelectZero Data Observability Platform currently deployed
  2. 2. Create a full backup of the current installation including configuration files and any data
  3. 3. Download SelectZero Data Observability Platform version 2025.5.2 or later from the official source (selectzero.io)
  4. 4. Follow the vendor's documented upgrade procedure to install version 2025.5.2
  5. 5. Verify the upgrade completed successfully by checking the version number in the platform
  6. 6. Test the login page to confirm that the text injection vulnerability has been remediated
  7. 7. Verify that user input on the login page is properly sanitized and no arbitrary text or HTML can be injected

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

Fix this in Selectzero Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52218 — 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-52218 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