← Back to results
Vulnerability record · public intelligence
CVE-2025-53121
UNKNOWN

Stored XSS in multiple 33.0.8files in opennms/opennms

Published Jun 26, 2025 · Updated Oct 23, 2026

Severity · CVSSUNKNOWN · Not scored
Known exploitationNot listed
EPSS / likelihood0.24%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Stored XSS in multiple 33.0.8files in opennms/opennms

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Multiple stored XSS were found on different nodes with unsanitized parameters in OpenMNS Horizon 33.0.8 and versions earlier than 33.1.6 on multiple platforms that allow an attacker to store on database and then inject HTML and/or Javascript on the page. The solution is to upgrade to Horizon 33.1.6, 33.1.7 or Meridian 2024.2.6, 2024.2.7 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. OpenNMS thanks Fábio Tomé for reporting this issue.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. GitHub advisory ↗
  2. Source repository ↗

Record history

Published Jun 26, 2025 · Last refreshed Oct 23, 2026