GHSA-p63h-7hw8-5cw4
MEDIUMGHSA-p63h-7hw8-5cw4 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.opennms:opennms. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-p63h-7hw8-5cw4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cross-Site Request Forgery in OpenNMS Horizon
Blast Radius
org.opennms:opennms☕org.opennms:opennms-configReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.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 CSRF, due to no CSRF protection, and since there is no validation of an existing user name while renaming a user. As a result, privileges of the renamed user are being overwritten by the old user and the old user is being deleted from the user list.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opennms:opennms | ≥ 1.0.0&&< 27.1.1 | 27.1.1 |
| ☕Maven | org.opennms:opennms-config | ≥ 1.0.0&&< 27.1.1 | 27.1.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opennms:opennms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.opennms:opennms to 27.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p63h-7hw8-5cw4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-p63h-7hw8-5cw4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-p63h-7hw8-5cw4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p63h-7hw8-5cw4 in your dependencies?
O3 detects GHSA-p63h-7hw8-5cw4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.