Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-0870: A form can be manipulated with cross-site request forgery in multiple versions of OpenNMS Meridian and Horizon

34
Routine
HIGH 8.1UPGRADEUPGRADE

CVE-2023-0870 is a high-severity flaw (CVSS 8.1) affecting horizon, meridian. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A form can be manipulated with cross-site request forgery in multiple versions of OpenNMS Meridian and Horizon. This can potentially allow an attacker to gain access to confidential information and compromise integrity. The solution is to upgrade to Meridian 2023.1.1 or Horizon 31.0.6 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be d

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorAdjacent network
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance0.3% (top 77%)
CISA exploited listNo
WeaknessCWE-352
Published2023-03-22
Last modified2026-06-17
Publisher (CNA): The OpenNMS Group · Vendor: opennms

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

opennms horizon UPGRADE
Affected: < 31.0.6
Fixed in: 31.0.6
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy horizon || rpm -q horizon || horizon --version
2. UPGRADE to 31.0.6 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade horizon
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade horizon
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
opennms meridian UPGRADE
Affected: >= 2020.1.0 and < 2020.1.33 · >= 2021.1.0 and < 2021.1.25 · >= 2022.1.0 and < 2022.1.14 · 2023.1.0
Fixed in: 2020.1.33, 2021.1.25, 2022.1.14
Safe to downgrade to: a release before 2020.1.0
1. Check installed version
apt-cache policy meridian || rpm -q meridian || meridian --version
2. UPGRADE to 2020.1.33 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade meridian
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade meridian
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2020.1.0 (Debian / Ubuntu)
apt-cache madison meridian sudo apt install meridian=<VERSION_BEFORE_2020.1.0> sudo apt-mark hold meridian
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list meridian sudo dnf downgrade meridian-<VERSION_BEFORE_2020.1.0> sudo dnf versionlock add meridian
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-0870?

horizon: upgrade to 31.0.6; meridian: upgrade to 2020.1.33, 2021.1.25, 2022.1.14. Exact commands for each OS are on this page.

Is CVE-2023-0870 being exploited?

CVE-2023-0870 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-0870 affect?

CVE-2023-0870 affects horizon, meridian. Severity is high (CVSS 8.1). A form can be manipulated with cross-site request forgery in multiple versions of OpenNMS Meridian and Horizon. This can potentially allow an attacker to gain access to confidential information and compromise integrity. The solution is to u

How urgent is CVE-2023-0870?

Priority 34/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.