LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25932: In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.0-1; OpenNMS Meridian, versions meridi...

In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.0-1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting, since the function `validateFormInput()` performs improper validation checks on the input sent to the `userID` parameter. Due to this flaw an attacker could inject an arbitrary script which will be stored in the database.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in OpenNMS Horizon and Meridian. A malicious user can submit script content in the userID field, which is saved in the database and may run later in another user's browser. The business concern is abuse of a trusted monitoring console and possible account/session misuse.

Executive priority

Treat this as a near-term hygiene fix for affected OpenNMS deployments, not an emergency based on the provided evidence. Prioritize faster if the console is internet-facing or accessible to many non-admin users.

Technical view

The source states validateFormInput() improperly validates input sent to the userID parameter, allowing arbitrary script to be stored in the database. Affected ranges include OpenNMS Horizon from opennms-1-0-stable through 27.1.0-1 and Meridian 2015.1.0-1 through 2019.1.18-1, plus 2020.1.0-1 through 2020.1.6-1.

Likely exposure

Exposure is limited to organizations running affected OpenNMS Horizon or Meridian versions, especially where account or user-management workflows are reachable by untrusted or lower-privileged users. Internet exposure is not stated in the sources and should be verified locally.

Exploitation context

The bundle identifies stored XSS but provides no CVSS score, CWE, proof of active exploitation, or KEV listing. Because KEV is false and no cited source states exploitation in the wild, active exploitation should not be assumed.

Researcher notes

Evidence is sparse. The CVE description names the vulnerable function and parameter, and references OpenNMS commits, but the bundle does not provide CVSS, exploit prerequisites, authentication requirements, or exact fixed release numbers.

Mitigation direction

  • Inventory OpenNMS Horizon and Meridian versions across monitoring environments.
  • Upgrade beyond the affected ranges after confirming OpenNMS vendor guidance.
  • Apply vendor packages containing the referenced OpenNMS code fixes.
  • Restrict administrative console access to trusted networks and users.
  • Review related release notes before changing production monitoring systems.

Validation and detection

  • Confirm whether any deployed version falls within the listed affected ranges.
  • Identify who can submit or modify userID values in OpenNMS.
  • Review stored user records for unexpected script-like content.
  • Check whether the OpenNMS console is reachable from untrusted networks.
  • Validate remediation against vendor advisories or patched package versions.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25932 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aOpenNMSopennms-1-0-stable,opennms-1.0.1 through opennms-27.1.0-1,meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1,meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.