# CVE-2021-25932: Cross-site scripting in OpenNMS

> Attackers can inject malicious scripts via the userID parameter in OpenNMS, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-78gg-3865-6f24

## What is CVE-2021-25932?

CVE-2021-25932 is a medium-severity cross-site scripting vulnerability in OpenNMS, published on 1 Jun 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

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

## Which versions are affected by CVE-2021-25932?

It affects 2 products.


Products: Opennms Meridian, Opennms Opennms.

## How do I fix CVE-2021-25932?

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

## Is CVE-2021-25932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25932 and fix it if it is affected.

What it is: CVE-2021-25932 is a medium-severity cross-site scripting vulnerability in OpenNMS, published on 1 Jun 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-25932 in the wild and no public exploit code.

Affected product: OpenNMS. 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-2021-25932/ (Markdown: https://insights.sbomify.com/CVE-2021-25932/index.md)
```

## Sources

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

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